[Bug 813767] New: Systemd does not work with LSB scripts for Open-Xchange 6.22
https://bugzilla.novell.com/show_bug.cgi?id=813767 https://bugzilla.novell.com/show_bug.cgi?id=813767#c0 Summary: Systemd does not work with LSB scripts for Open-Xchange 6.22 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 64bit OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rm@anracon.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 About 2 weeks ago I successfully upgraded from Open-Xchange 6.20.7 to 6.22.0 and further to 6.22.1. All on an Opensuse 12.2 (x86_64) system - no problems with activating the open-xchange-daemon by using systemd (systemctl) there. Now, I have in addition upgraded the system to Opensuse 12.3. While this was a surprisingly smooth transition for almost all server components, there is real trouble with systemd and OX 6.22. There is no chance to start OX 6.22 with systemd on Opensuse 12.3. At least not on my system and at least not after the last updates (of systemd). (It may have been different on the freshly installed OS 12.3 but I am not 100% sure about that). The situation right now is the following: After starting OX by "systemctl start open-xchange" the status of the open-xchange LSB service is displayed as follows: mysystem:/etc/init.d # systemctl status open-xchange.service open-xchange.service – LSB: Open Xchange Daemon Loaded: loaded (/etc/init.d/open-xchange) Active: inactive (dead) since Wed, 2013-03-27 12:30:19 CET; 5min ago Process: 13365 ExecStop=/etc/init.d/open-xchange stop (code=exited, status=0/SUCCESS) Process: 13349 ExecStart=/etc/init.d/open-xchange start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/open-xchange.service Mar 27 12:30:19 mysystem.mydomain.de systemd[1]: Starting LSB: Open Xchange Daemon… Mar 27 12:30:19 mysystem.mydomain.de open-xchange[13349]: Starting open-xchange ..done Mar 27 12:30:19 mysystem.mydomain.de systemd[1]: Started LSB: Open Xchange Daemon. Mar 27 12:30:19 mysystem.mydomain.de su[13360]: (to open-xchange) root on none Mar 27 12:30:19 mysystem.mydomain.de open-xchange[13365]: Shutting down open-xchange ..done The service is dead, according to systemd. The start was directly followed by a stop of the service. However, starting OX manually by the script "/etc/init.d/open-xchange start" works perfectly, if you are in the directory /etc/init.d : mysystem:/etc/init.d # ./open-xchange start redirecting to systemctl start Starting open-xchange done mysystem:/etc/init.d # ./open-xchange status Checking for service open-xchange running Checking for service open-xchange running But systemd does not take notice of this success : mysystem:/etc/init.d # systemctl status open-xchange open-xchange.service – LSB: Open Xchange Daemon Loaded: loaded (/etc/init.d/open-xchange) Active: inactive (dead) since Wed, 2013-03-27 12:57:05 CET; 1min 39s ago So, it seems that there is no communication between systend and open-xchange - neither when using systemctl to start OX nor when using systemctl to ask for the status. Consistently, activating open-xchange by using the "runlevel editor" of YaST does not work either. Furthermore, a strange thing is the following: Even an "rcopen-xchange start" (stop, status) does not work. And "rcopen-xchange" is just a link to "/etc/init.d/open-xchange". The only way for me to start OX is via changing (as root) to the directory "/etc/init.d" and use "./open-xchange start" there. Things do not work in case I am in a different directory and use "/etc/init.d/open-xchange start". Where does this dependency on the directory come from ? For the time being it looks as if I must start OX manually under Opensuse 12.3 after booting - a situation, which I do not like. Any ideas why systemd in contrast to OS 12.2 is not working with OX 6.22 under OS 12.3 ? Reproducible: Always Steps to Reproduce: 1. Install Open-Xchange 6.22 with the corresponding LSB start/stop-scripts 2. Try starting open-xchange by systemctl 3. Actual Results: The service is never started or maybe started and directly afterwards stopped Expected Results: The result of systemctl should be the same as when using ./open-xchange start in /etc/init.d - namely a running open-xchange service -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c1
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c2
Ralph Moenchmeyer
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c3
--- Comment #3 from Ralph Moenchmeyer
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c4
--- Comment #4 from Ralph Moenchmeyer
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c
FeiXiang Zhang
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c5
--- Comment #5 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c6
Ralph Moenchmeyer
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c7
--- Comment #7 from Ralph Moenchmeyer
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c8
--- Comment #8 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c9
--- Comment #9 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c10
--- Comment #10 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c11
--- Comment #11 from Frederic Crozat
su is the wrong tool to start daemons and it's not really meant to be used non-interactively anyways. So don't do that. better use startproc/start_daemon instead or have the daemon handle the user switching itself.
agreed but startproc can't be used in this particular case, because OX is java code and startproc doesn't work great with that. I highly suggest using the systemd service solution instead.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c12
--- Comment #12 from Ralph Moenchmeyer
Please install this file in /etc/systemd/system and run: systemctl daemon-reload systemctl enable open-xchange.service
and then test systemctl start open-xchange.service
I assume that by "install" you mean just copy the file to /etc/system.d/system as "open-xchange.service". Which I did - plus: # systemctl daemon-reload # systemctl enable open-xchange.service This ended with # systemctl enable open-xchange The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). Indeed your service-file lacks an "install" section. Enabling the service with YaST2 (for a start at boottime) does not work either. I assume that therefore the service cannot be started with systemd despite your file. The status again is stopped after booting. Any suggestions to remedy that? However, on a running system # systemctl start open-xchange.service works as expected - which is already progress. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c13
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c14
--- Comment #14 from Ralph Moenchmeyer
mysys:~ # rcopen-xchange status
Checking for service open-xchange dead open-xchange.service Loaded: loaded (/etc/systemd/system/open-xchange.service; enabled) Active: active (running) since Tue, 2013-06-04 09:11:12 CEST; 11min ago Main PID: 3454 (java) CGroup: name=systemd:/system/open-xchange.service └ 3454 /usr/bin/java -Xmx512m -XX:+UseConcMarkSweepGC -XX:MaxPermSize=128M -Dsun.net.inetad... Jun 04 09:11:12 mysys systemd[1]: Starting open-xchange.service... Jun 04 09:11:12 mysys systemd[1]: Started open-xchange.service. <<<< However:
mysys:~ # systemctl status open-xchange.service open-xchange.service Loaded: loaded (/etc/systemd/system/open-xchange.service; enabled) Active: active (running) since Tue, 2013-06-04 09:11:12 CEST; 11min ago Main PID: 3454 (java) CGroup: name=systemd:/system/open-xchange.service └ 3454 /usr/bin/java -Xmx512m -XX:+UseConcMarkSweepGC -XX:MaxPermSize=128M -Dsun.net.inetad...
Jun 04 09:11:12 mysys systemd[1]: Starting open-xchange.service... Jun 04 09:11:12 mysys systemd[1]: Started open-xchange.service. <<<<<< Whilst the starting dead message of rcopen-xchange is not a real problem it may lead to confusion - especially when you have scripts running that evaluate the answer of "rcopen-xchange status". 2) Failed state message when stopping the service *************************************************** There is a confusing statement after a stop of the service:
mysys:~ # systemctl stop open-xchange.service mysys:~ # systemctl status open-xchange.service open-xchange.service Loaded: loaded (/etc/systemd/system/open-xchange.service; enabled)
Active: failed (Result: exit-code) since Tue, 2013-06-04 09:34:54 CEST; 3s ago Process: 6803 ExecStart=/opt/open-xchange/sbin/open-xchange (code=exited, status=143) CGroup: name=systemd:/system/open-xchange.service Jun 04 09:34:45 mysys systemd[1]: Starting open-xchange.service... Jun 04 09:34:45 mysys systemd[1]: Started open-xchange.service. Jun 04 09:34:51 mysys systemd[1]: Stopping open-xchange.service... Jun 04 09:34:54 mysys systemd[1]: open-xchange.service: main process exited, code=exited, status=143/n/a Jun 04 09:34:54 mysys systemd[1]: Stopped open-xchange.service. Jun 04 09:34:54 mysys systemd[1]: Unit open-xchange.service entered failed state <<<<<< The messages about a "failed state" are somewhat unusual and disturbing. Could you shortly explain where this comes from ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c15
--- Comment #15 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c16
--- Comment #16 from Ralph Moenchmeyer
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c17
--- Comment #17 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c18
--- Comment #18 from Carsten Hoeger
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c19
--- Comment #19 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=813767
https://bugzilla.novell.com/show_bug.cgi?id=813767#c
Frederic Crozat
participants (1)
-
bugzilla_noreply@novell.com