Re: [SOGo] sogo fails to start
Hi, Am 09.11.15 um 03:37 schrieb Nigel Pegram: > Hi, > > I have a previously working sogo install which following an upgrade now > fails to start. > > It displays the error message: sogod[26952] File NSData.m: 163. In > readContentsOfFile Open ((null)) attempt failed - bad path From which version to which did you upgrade? and debugging/more verbose logs can be enabled: http://www.sogo.nu/nc/support/faq/article/how-to-enable-more-verbose-logging-in-sogo.html regards . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82420 E-Mail goetz.reini...@filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] sogo fails to start
I remembered I had changed one item in the setup file, so upon reverting that, and enabling more debugging options the logs display: version 2.3.2 (build @shiva.inverse 201509161658) -- starting vmem size check enabled: shutting down app when vmem > 384 MB <0x0x7f3e9ebac288[SOGoProductLoader]> SOGo products loaded from '/usr/lib/GNUstep/SOGo': <0x0x7f3e9ebac288[SOGoProductLoader]> Appointments.SOGo, CommonUI.SOGo, MailPartViewers.SOGo, MailerUI.SOGo, ContactsUI.SOGo, PreferencesUI.SOGo, Contacts.S OGo, MainUI.SOGo, SchedulerUI.SOGo, AdministrationUI.SOGo, Mailer.SOGo 2015-11-09 12:25:29.916 sogod[3115] WOContext.m:85 Assertion failed in WOContext(instance), method initialize. Couldn't instantiate WOContextClass ((null))! /usr/sbin/sogod: Uncaught exception NSInternalInconsistencyException, reason: WOContext.m:85 Assertion failed in WOContext(instance), method initialize. Cou ldn't instantiate WOContextClass ((null))! TIA Nigel On 09/11/15 10:37, Nigel Pegram wrote: Hi, I have a previously working sogo install which following an upgrade now fails to start. It displays the error message: sogod[26952] File NSData.m: 163. In readContentsOfFile Open ((null)) attempt failed - bad path I'm unsure how to debug this. Any pointers appreciated. TIA Nigel -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] sogo fails to start
Removal and reinstallation of sogo fixed problem. Thanks anyway. On 09/11/15 10:37, Nigel Pegram wrote: Hi, I have a previously working sogo install which following an upgrade now fails to start. It displays the error message: sogod[26952] File NSData.m: 163. In readContentsOfFile Open ((null)) attempt failed - bad path I'm unsure how to debug this. Any pointers appreciated. TIA Nigel -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] sogo fails to start
Hi, I have a previously working sogo install which following an upgrade now fails to start. It displays the error message: sogod[26952] File NSData.m: 163. In readContentsOfFile Open ((null)) attempt failed - bad path I'm unsure how to debug this. Any pointers appreciated. TIA Nigel -- users@sogo.nu https://inverse.ca/sogo/lists
RE: RE: [SOGo] SOGo fails to start on fresh installation after reboot
Hello, > any news about this problem? > I got the same kind with centos 7. > But the solutions with touch and chown is not working. > I got this by systemctl : > Sep 23 11:53:51 mail systemd[1]: Failed to read PID from file /var/run/sogo/ > sogo.pid: Invalid argument I still do not have a workaround better than touch&chown. With best regards, P. Trifonov -- users@sogo.nu https://inverse.ca/sogo/lists
Re: RE: [SOGo] SOGo fails to start on fresh installation after reboot
Hello,
any news about this problem?
I got the same kind with centos 7.
But the solutions with touch and chown is not working.
I got this by systemctl :
sogod.service - SOGo is a groupware server
Loaded: loaded (/usr/lib/systemd/system/sogod.service; enabled)
Active: inactive (dead) since Wed 2015-09-23 11:53:56 UTC; 2min 14s ago
Process: 12401 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -
WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
(code=exited, status=0/SUCCESS)
Main PID: 12402 (code=exited, status=0/SUCCESS)
Sep 23 11:53:50 mail systemd[1]: Starting SOGo is a groupware server...
Sep 23 11:53:51 mail systemd[1]: Failed to read PID from file /var/run/sogo/
sogo.pid: Invalid argument
Sep 23 11:53:51 mail systemd[1]: Started SOGo is a groupware server.
Thank you,
Hoggart Simon
--
users@sogo.nu
https://inverse.ca/sogo/lists
RE: [SOGo] SOGo fails to start on fresh installation after reboot
Hello, > 2015-07-23 15:27:54.346 sogod[5522] File NSData.m: 1436. In -[NSData > writeToFile:options:error:] Open (/var/run/sogo/sogo.pid) failed - No such > file or directory Jul 23 15:27:54 sogod [5522]: [ERROR] > <0x0x7f6ab8ebb0a0[NSUserDefaults]> > unable to open pid file: /var/run/sogo/sogo.pid > Has anyone experienced this? I have the same problem on FreeBSD 9.1. In my case it helps to run touch /var/run/sogo/sogo.pid ; chown sogo /var/run/sogo/sogo.pid before starting sogod. I am still looking for a better solution. With best regards, P. Trifonov -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] SOGo fails to start on fresh installation after reboot
Hi All,
I'm having an issue with installing SOGo on top of iRedMail 9.2 + OpenLDAP on
CentOS 7 x86_64.
iRedMail and OpenLDAP are functioning correctly to the best of my knowledge (I
can login, create users, write/receive emails from them etc.). I'll also have
you know that I have successfully installed SOGo ontop of iRedMail 9.2 + MySQL
on Centos 6.6 x86_64. I didn't have any issues rebooting and restarting the
sogo daemon there.
Specifically, after a fresh install of SOGo (which runs fine initially), when
doing a reboot, the following occurs when it tries to start the SOGo service:
systemctl status sogod.service:
sogod.service - SOGo is a groupware server
Loaded: loaded (/usr/lib/systemd/system/sogod.service; enabled)
Active: failed (Result: resources) since Thu 2015-07-23 15:27:54 EDT; 24min
ago
Process: 5521 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -
WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
(code=exited, status=0/SUCCESS)
Jul 23 15:27:54 mail2.infogisticsit.com systemd[1]: Starting SOGo is a
groupware server...
Jul 23 15:27:54 mail2.infogisticsit.com systemd[1]: PID file /var/run/sogo/
sogo.pid not readable (yet?) after start.
Jul 23 15:27:54 mail2.infogisticsit.com systemd[1]: sogod.service never wrote
its PID file. Failing.
Jul 23 15:27:54 mail2.infogisticsit.com systemd[1]: Failed to start SOGo is a
groupware server.
Jul 23 15:27:54 mail2.infogisticsit.com systemd[1]: Unit sogod.service entered
failed state.
sogo.log:
2015-07-23 15:27:54.346 sogod[5522] File NSData.m: 1436. In -[NSData
writeToFile:options:error:] Open (/var/run/sogo/sogo.pid) failed - No such
file or directory
Jul 23 15:27:54 sogod [5522]: [ERROR] <0x0x7f6ab8ebb0a0[NSUserDefaults]>
unable to open pid file: /var/run/sogo/sogo.pid
The only information I've found similar to this through searching google was
with apache doing a similar thing. It turned out the PID file needed to be
symlinked somewhere else. The solution didn't quite seem applicable here,
especially considering I couldn't find sogo.pid elsewhere.
Has anyone experienced this?
Thank you!
-Curtis
--
users@sogo.nu
https://inverse.ca/sogo/lists
