0003686: In CentOS 7 sogod does not start after mariadb reliably - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0003686	SOGo	Packaging (RedHat)	public	2016-05-20 13:34	2016-05-24 14:46

Reporter	florian	Assigned To	plevesque
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	resolved	Resolution	fixed
Product Version	3.1.0
Fixed in Version	3.1.1

Summary	0003686: In CentOS 7 sogod does not start after mariadb reliably
Description	In CentOS 7 sogod does not start after mariadb reliably which makes sogo processes fail with error like this: May 20 15:16:15 sogod [1633]: [ERROR] <0x0x7fc05aef6b30[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x7fc05aff3770] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile Solution: modify service configuration in sogo package to make sogod.service start AFTER mariadb.service. In /etc/systemd/system/multi-user.target.wants/sogod.service add a line in [Unit] section: After=mariadb.service
Tags	No tags attached.

Date Modified	Username	Field	Change
2016-05-20 13:34	florian	New Issue
2016-05-20 15:01	ludovic	Assigned To	=> plevesque
2016-05-20 15:01	ludovic	Status	new => assigned
2016-05-24 14:35	plevesque	Note Added: 0010207
2016-05-24 14:35	plevesque	Status	assigned => resolved
2016-05-24 14:35	plevesque	Fixed in Version	=> nightly v2
2016-05-24 14:35	plevesque	Resolution	open => fixed
2016-05-24 14:46	francis	Fixed in Version	nightly v2 => 3.1.1

plevesque 2016-05-24 14:35 reporter ~0010207	Dependency added to the master versions on v3 and v2: https://github.com/inverse-inc/sogo/commit/8225a4ccb0b6839b09c56c66fec0f6227e4389af https://github.com/inverse-inc/sogo/commit/87c7e64c898fdbf477729c30bdf383e64e35a53a Will appear in the next nightly builds, then in the next releases of SOGo v3 and SOGo v2.