Topic: SOGo missing table, Weird behavior
==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
======== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====
Hello,
After upgrading Ubuntu from 14.04 to 16.04, SOGo has been acting weird.
First, the log in page changed (no css?) as it now looks like the attached file (sogo.png) - notice the spinning wheel at the bottom left.
Filling in login info and clicking connect does nothing.
-A cron job that runs every minute, sends mail to postmaster everyminute, filling up my inbox.
The email says:
Subject: Cron <sogo@mailserver> /usr/sbin/sogo-tool expire-sessions 30; /usr/sbin/sogo-ealarms-notify
2016-11-17 18:20:08.712 sogo-ealarms-notify[468] ERROR: could not open MySQL4 connection to database 'sogo': Can't connect to MySQL server on '27.0.0.1' (110)
<0x0x117f770[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x10dc7e0] connection=0x(null)> for mysql://27.0.0.1/sogo/sogo_alarms_folder
<0x0x117f770[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2016-11-17 18:18:01 -0500
2016-11-17 18:22:15.944 sogo-ealarms-notify[468] ERROR: could not open MySQL4 connection to database 'sogo': Can't connect to MySQL server on '27.0.0.1' (110)
<0x0x117f770[GCSChannelManager]> could not open channel <MySQL4Channel[0x0xf87900] connection=0x(null)> for mysql://27.0.0.1/sogo/sogo_alarms_folder
<0x0x117f770[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2016-11-17 18:20:08 -0500
I changed "ALL" root cron jobs and added 2>&1 to them so the mails would stop, and nothing.
Then I noticed that the table sogo_alarms_folder does not exist in the sogo DB.
Restarting Sogo did not create that table either.
I tried commenting out the ling in sogo.conf that mentions that table, restarted sogo, no change.
//OCSEMailAlarmsFolderURL = "mysql://sogo:<password>@127.0.0.1:3306/sogo/sogo_alarms_folder";
- /var/log/mysql shows this error every minute as well:
2016-11-17T23:25:01.172004Z 705 [Note] Aborted connection 705 to db: 'sogo' user : 'sogo' host: 'localhost' (Got an error reading communication packets)
-logging in manually to mysql with user sogo works fine.
I am using the sogo conf file here: http://pastebin.com/7XevuLAn
My main concern is stopping the incoming mail from sogo@mailserver. Getting Sogo to work again is a plus at this point since I got my clients using IMAP on their mail clients
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.