Hi,
We're running sogo v5 on debian. Last tuesday we upgraded from stretch
to buster. Ever since, mysql started giving errors for every run of the
sogo-ealarms-notify cronjob:
Sep 17 11:56:01 sogo CRON[6311]: (sogo) CMD (/usr/sbin/sogo-ealarms-notify > /dev/null
2>&1)
mysql [Warning] Aborted connection 148 to db: 'sogo-db' user: 'sogo-user' host:
'localhost' (Got an error reading communication packets)
Database connectivity otherwise works fine: /SOGo and ActiveSync
interface works, calenders/contacts are all displayed without issues.
For the record: After the upgrade from we also changed to the buster
SOGo repo. Today we also tried with the latest v5 nightlies to see if
that fixes this, but alas: no.
Buster comes with mariadb-server-10.3, which we are running, using the
'traditional' (old style) sogo database layout.
Installed sogo packages:
# apt-show-versions|grep -e sogo
sogo:amd64/buster 5.0.0.20200917-1 uptodate
sogo-activesync:amd64/buster 5.0.0.20200917-1 uptodate
# apt-show-versions|grep -e sope
libsope-appserver4.9:amd64/buster 4.9.r1664.20200915 uptodate
libsope-core4.9:amd64/buster 4.9.r1664.20200915 uptodate
libsope-gdl1-4.9:amd64/buster 4.9.r1664.20200915 uptodate
libsope-ldap4.9:amd64/buster 4.9.r1664.20200915 uptodate
libsope-mime4.9:amd64/buster 4.9.r1664.20200915 uptodate
libsope-xml4.9:amd64/buster 4.9.r1664.20200915 uptodate
sope4.9-dbg:amd64/buster 4.9.r1664.20200915 uptodate
sope4.9-gdl1-mysql:amd64/buster 4.9.r1664.20200915 uptodate
sope4.9-libxmlsaxdriver:amd64/buster 4.9.r1664.20200915 uptodate
Anyone with an idea what to look for / where to look at?
Why would the sogo-ealarms-notify cause this problem, while the regular
sogo components works fine? Anyone else seeing this?
Hope to get some insights here! Thanks! :-)
MJ
--
users@sogo.nu
https://inverse.ca/sogo/lists
