sogo crash?

[ChessSpider]

it was unreachable

root@71d815832dc0:/# ps -aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.2  58164  8232 ?        Ss   Sep19   0:48 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor/supervisord.conf
root         8  0.0  0.0 365644  1712 ?        Sl   Sep19   0:21 /usr/sbin/syslog-ng --foreground --no-caps
root         9  0.0  0.0  27992  1300 ?        S    Sep19   0:01 /usr/sbin/cron -f
root        10  0.0  0.0  18016  2148 ?        S    Sep19   0:00 /bin/bash /reconf-domains.sh
sogo        11  0.0  0.1  38552  4748 ?        S    Sep19   0:18 /usr/bin/python -u -m SimpleHTTPServer 9192
sogo        26  0.0  1.4 342820 58016 ?        Ss   Sep19   0:33 /usr/sbin/sogod
root     15315  0.0  0.0   4196   672 ?        S    15:37   0:00 sleep 99999
root     16082  0.1  0.0  18188  3324 pts/0    Ss   17:15   0:00 /bin/bash
root     16395  0.0  0.0  36632  2820 pts/0    R+   17:15   0:00 ps -aux

nginx log

sogo-mailcow_1       | Sep 20 17:12:01 71d815832dc0 CRON[16054]: (sogo) CMD (  /usr/sbin/sogo-ealarms-notify 2>/dev/null)
sogo-mailcow_1       | Sep 20 17:12:01 71d815832dc0 CRON[16052]: pam_unix(cron:session): session closed for user sogo
sogo-mailcow_1       | Sep 20 17:12:02 71d815832dc0 CRON[16051]: pam_unix(cron:session): session closed for user sogo
sogo-mailcow_1       | Sep 20 17:13:01 71d815832dc0 CRON[16059]: pam_unix(cron:session): session opened for user sogo by (uid=0)
sogo-mailcow_1       | Sep 20 17:13:01 71d815832dc0 CRON[16060]: pam_unix(cron:session): session opened for user sogo by (uid=0)
sogo-mailcow_1       | Sep 20 17:13:01 71d815832dc0 CRON[16064]: (sogo) CMD (  /usr/sbin/sogo-ealarms-notify 2>/dev/null)
sogo-mailcow_1       | Sep 20 17:13:01 71d815832dc0 CRON[16062]: (sogo) CMD (  /usr/sbin/sogo-tool expire-sessions 60)
sogo-mailcow_1       | Sep 20 17:13:01 71d815832dc0 CRON[16059]: pam_unix(cron:session): session closed for user sogo
sogo-mailcow_1       | Sep 20 17:13:01 71d815832dc0 CRON[16060]: pam_unix(cron:session): session closed for user sogo
sogo-mailcow_1       | Sep 20 17:14:01 71d815832dc0 CRON[16067]: pam_unix(cron:session): session opened for user sogo by (uid=0)
sogo-mailcow_1       | Sep 20 17:14:01 71d815832dc0 CRON[16068]: pam_unix(cron:session): session opened for user sogo by (uid=0)
sogo-mailcow_1       | Sep 20 17:14:01 71d815832dc0 CRON[16072]: (sogo) CMD (  /usr/sbin/sogo-ealarms-notify 2>/dev/null)
sogo-mailcow_1       | Sep 20 17:14:01 71d815832dc0 CRON[16070]: (sogo) CMD (  /usr/sbin/sogo-tool expire-sessions 60)
sogo-mailcow_1       | Sep 20 17:14:01 71d815832dc0 CRON[16067]: pam_unix(cron:session): session closed for user sogo
sogo-mailcow_1       | Sep 20 17:14:01 71d815832dc0 CRON[16068]: pam_unix(cron:session): session closed for user sogo
nginx-mailcow_1      | 2017/09/20 15:13:00 [error] 9#9: *34744 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.18.0.2, server: mail.example.com, request: "GET /SOGo HTTP/1.1", upstream: "http://172.22.1.252:20000/SOGo", host: "mail.example.com"

updated on 17 09 2017

[andryyy]

I think we have an issue for this, iirc.

This is still not the new container. We don't have a reconf-domains.sh anymore.

[DrTrills]

I also got a SOGo crash..updating now and will keep an eye on it

[ChessSpider]

duplicate of https://github.com/mailcow/mailcow-dockerized/issues/538