[mythtv] Systemd expertise needed: systemctl fails to start mythbackend
R. G. Newbury
newbury at mandamus.org
Thu Jul 5 03:28:20 UTC 2012
Figured I would start by asking here, as google is no help.
This is on Fedora 17, new install and master trunk from this afternoon.
systemd actually starts mysqld in fedora 17, which it ceased to do in
f16. But the same sort of problem appears with mythbackend. Systemctl
fails to start mythbackend. Which is really weird because mythbackend
will quite happily and properly using the *same* command line which is
in the service file. Systemd is doing/not doing something and
mythbackend starts and then dies. mythlogserver starts and stays.
Here is mythbackend started from the command line:
[ root at tor6 sbin] /usr/local/bin/mythbackend --syslog --loglevel crit
--pidfile /run/mythtv/backend.pid
2012-07-04 22:48:35.758620 C mythbackend version: master
[v0.26-pre-742-gb6d65fc-dirty] www.mythtv.org
2012-07-04 22:48:35.758658 C Qt version: compile: 4.8.2, runtime: 4.8.2
2012-07-04 22:48:35.758664 N Enabled verbose msgs: general
And ps output
[ root at tor6 sbin] ps -ae
3158 ? 00:00:01 mythlogserver
3207 pts/4 00:00:00 mythcommflag
3230 pts/4 00:00:00 mythbackend
3273 pts/4 00:00:00 mythcommflag
3292 pts/3 00:00:00 ps
And here is the systemctl result: (tried both with and without --daemon:
this is without)
[root at tor6 sbin]# systemctl start mythbackend.service
**** Note there is no error message here!
[root at tor6 sbin]# systemctl status mythbackend.service
mythbackend.service - mythbackend daemon
Loaded: loaded (/usr/lib/systemd/system/mythbackend.service;
enabled)
Active: failed (Result: exit-code) since Wed, 04 Jul 2012
22:51:38 -0400; 13s ago
Process: 3348 ExecStart=/usr/local/bin/mythbackend --daemon
--syslog --loglevel crit (code=exited, status=0/SUCCESS)
Main PID: 3350 (code=exited, status=130)
CGroup: name=systemd:/system/mythbackend.service
3207 pts/4 00:00:00 mythcommflag
3273 pts/4 00:00:00 mythcommflag
3304 ? 00:00:01 mythlogserver
It reports success but then partially fails.
Here is the only clue that I have: when started by systemctl mythbackend
acts like it is not properly configured
.
[root at tor6 sbin] tail -5 /var/log/messages
Jul 4 22:55:14 tor6 mythbackend[3505]: No UPnP backends found
Jul 4 22:55:14 tor6 mythbackend[3505]: Would you like to configure the
database connection now? [no]
Jul 4 22:55:14 tor6 mythbackend[3505]: [console is not interactive,
using default 'no']
Jul 4 22:55:15 tor6 systemd[1]: mythbackend.service: main process
exited, code=exited, status=130
Jul 4 22:55:15 tor6 systemd[1]: Unit mythbackend.service entered failed
state.
That response is NOT returned when started at the commandline.
Any answers, ideas, WAG's or even DIT's accepted.
This is not fatal but it is bothersome!
Geoff
More information about the mythtv-dev
mailing list