You are not logged in. Please login or register.
iRedMail → iRedMail Support → SOGo 3.0.1
By the way, i created a tutorial for upgrading sogo, did you miss any steps mentioned in the tutorial? Or, does the tutorial miss any steps?
http://www.iredmail.org/docs/upgrade.sogo.2.to.3.html
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.Cannot start sogod, no any log in /var/log/sogo/sogo.log?
The last logs from sogod:
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0bb8b20[WOWatchDogChild]> sending terminate signal to pid 328 │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0bb8840[WOWatchDogChild]> sending terminate signal to pid 325 │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0c54f30[WOWatchDog]> Terminating with SIGINT or SIGTERM │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0bb9150[WOWatchDogChild]> child 331 exited │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0c54f30[WOWatchDog]> Terminating with SIGINT or SIGTERM │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0be56e0[WOWatchDogChild]> child 332 exited │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0c54f30[WOWatchDog]> Terminating with SIGINT or SIGTERM │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0bee4d0[WOWatchDogChild]> child 333 exited │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0c54f30[WOWatchDog]> Terminating with SIGINT or SIGTERM │
Mar 25 16:19:40 sogod [253]: <0x0x7f2dd0bef050[WOWatchDogChild]> child 14342 exited Nothing for the last day after attempting upgrade.
Also in journalctl -xe:
Mar 27 16:50:01 mail CROND[11885]: (root) CMD (/usr/bin/python /opt/iredapd/tools/spf_to_greylisting_whitelists.py &>/dev/null)
Mar 27 16:51:01 mail crond[151]: (sogo) ERROR (getpwnam() failed)
Mar 27 16:51:47 mail clamd[125]: SelfCheck: Database status OK.
Mar 27 16:51:47 mail clamd[125]: SelfCheck: Database status OK.
Mar 27 16:52:01 mail crond[151]: (sogo) ERROR (getpwnam() failed)
Mar 27 16:53:01 mail crond[151]: (sogo) ERROR (getpwnam() failed)
Mar 27 16:54:01 mail crond[151]: (sogo) ERROR (getpwnam() failed)
Mar 27 16:55:01 mail crond[151]: (sogo) ERROR (getpwnam() failed)
Mar 27 16:56:01 mail crond[151]: (sogo) ERROR (getpwnam() failed)
Mar 27 16:57:01 mail crond[151]: (sogo) ERROR (getpwnam() failed)
Mar 27 16:57:35 mail systemd[1]: Stopping System Logging Service...Some more:
Mar 26 17:01:01 mail postfix/proxymap[709]: warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (111)
Mar 26 17:01:01 mail postfix/trivial-rewrite[781]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Mar 26 17:01:01 mail postfix/trivial-rewrite[781]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Mar 26 17:01:01 mail postfix/proxymap[709]: warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (111)
Mar 26 17:01:01 mail postfix/cleanup[768]: warning: proxy:mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf lookup error for "sogo@mail.domain.com"
Mar 26 17:01:01 mail postfix/cleanup[768]: warning: A909D240507: sender_bcc_maps lookup problem
Mar 26 17:01:01 mail postfix/pickup[700]: warning: maildrop/8C2B2240505: error writing A909D240507: queue file write errorLooks like all logging has switched to console on this Centos 7.2 system.
Mar 26 17:01:01 mail postfix/trivial-rewrite[781]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Is MySQL service running? Postfix cannot query sql server.
Your upgrading process is different than mine. I didn't experience similar issue like yours. i did the upgrade on @iredmail.org, one issue arose, and several people reported the same issue in SOGo mailing list, all were fixed by reinstall package "sope" (uninstall "sope" will remove sogo packages too).
dsp3 wrote:Mar 26 17:01:01 mail postfix/trivial-rewrite[781]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Is MySQL service running? Postfix cannot query sql server.
Your upgrading process is different than mine. I didn't experience similar issue like yours. i did the upgrade on @iredmail.org, one issue arose, and several people reported the same issue in SOGo mailing list, all were fixed by reinstall package "sope" (uninstall "sope" will remove sogo packages too).
The rest of iRemail is working ok, as I have Roundcube installed and it's working without issue (mysql).
I have removed SOGo and Sope packages and deleted the sogo user. What remains are the cron jobs. Can you give me a quick reference on removing these? Thanks.
crond[151]: (sogo) ERROR (getpwnam() failed)You can manage the cron jobs with command:
crontab -e -u sogodIf you removed sogod user, please check file /var/cron/tabs/sogod instead.
You can manage the cron jobs with command:
crontab -e -u sogodIf you removed sogod user, please check file /var/cron/tabs/sogod instead.
Thanks. /var/spool/cron/sogo on Centos. Sogo removed for now. Will try again in the future.
iRedMail → iRedMail Support → SOGo 3.0.1
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 2 official extensions. Copyright © 2003–2010 PunBB.
Generated in 0.008 seconds (56% PHP - 44% DB) with 10 queries