Am 16.06.2017 um 16:23 schrieb mj ([email protected]): > Hi, > > We're using a sogo3 test machine, connected to the database on our sogo2 > production server. > > This config shows in the following ERROR in sogo.log: >> 2017-06-16 16:11:53.134 sogod[900] ERROR: could not open MySQL4 >> connection to database 'sogo': Can't connect to local MySQL server >> through socket '/var/run/mysqld/mysqld.sock' (2) >> Jun 16 16:11:53 sogod [900]: [ERROR] >> <0x0x56330c265840[GCSChannelManager]> could not open channel >> <MySQL4Channel[0x0x56330c5fdce0] connection=0x(null)> for >> mysql://localhost/sogo/sogotest0013e591e17 >> Jun 16 16:11:53 sogod [900]: [WARN] >> <0x0x56330c265840[GCSChannelManager]> will prevent opening of this >> channel 5 seconds after 2017-06-16 16:11:53 +0200 >> Jun 16 16:11:53 sogod [900]: [ERROR] <0x0x56330c609a70[GCSFolder]> >> could not open storage channel! > > The mysql config in sogo.conf looks like this: >> root@sogo3:/etc/sogo# cat sogo.conf >> { >> OCSFolderInfoURL = >> "mysql://username:[email protected]:3306/sogo/sogo_folder_info"; >> SOGoProfileURL = >> "mysql://username:[email protected]:3306/sogo/sogo_user_profile"; >> >> OCSSessionsFolderURL = >> "mysql://username:[email protected]:3306/sogo/sogo_sessions_folder"; >> >> OCSEMailAlarmsFolderURL = >> "mysql://username:[email protected]:3306/sogo/sogo_alarms_folder"; >> > > Things DO work, so I guess it also connects to the correct database > location, but the error message seems strange..? > > MJ
You just experience the downside of sogo storing database informations in the database itself. See Tip at https://sogo.nu/files/docs/SOGoInstallationGuide.html#_database_configuration Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
