How to "nuke" mythtv logserver daemon?

Quakeboy02 · 11-18-2015, 03:48 PM

I continue to have problems where mythbackend stops, or at least becomes unresponsive, and the only way to recover mythtv is to nuke mythlogserver.

I added the following to /etc/init.d/mythtv-backend but...

Code:

  nuke)
        echo -n "Nuking myth "
        ps -ef |grep myth |grep -v grep | grep -v init\.d |awk '{print $2}' |xargs kill -9
        ;;

I get the following complaint.

Code:

bob@musem:~$ sudo /etc/init.d/mythtv-backend restart
[....] Restarting mythtv-backend (via systemctl): mythtv-backend.serviceWarning: Unit file of mythtv-backend.service changed on disk, 'systemctl daemon-reload' recommended.

I don't get this complaint when I manually "kill -9" the mythlogserver after using "/etc/init.d/mythtv-backend stop". I've tried using the "...stop" command before running nuke, but I still get the complaint about systemctl. So, is this a sequencing problem or am I going about this the wrong way?

The problem is on debian jessie, but it's the same on all the debian releases I've used over the years. So, I'd like to have a way of doing this through init.d.

berndbausch · 11-18-2015, 05:16 PM

When you modify startup scripts, you should tell the corresponding services that they need to reread them. That's what "reload" means. "systemctl daemon-reload" just tells all services to reread their config.

So, after editing, just do as the warning message suggests; perhaps that settles it.It's a bit strange though that you get the message at restart, which includes reload afaik.

Now I don't know if your approach of modifying init.d is valid when your system uses systemd. You might want to look for a tutorial how to write startup code under systemd.

Quakeboy02 · 11-18-2015, 05:27 PM

Quote:

Originally Posted by berndbausch

When you modify startup scripts, you should tell the corresponding services that they need to reread them. That's what "reload" means. "systemctl daemon-reload" just tells all services to reread their config.

Thanks! I was wondering about that, but failed to test for it. My bad.

Quote:

Now I don't know if your approach of modifying init.d is valid when your system uses systemd. You might want to look for a tutorial how to write startup code under systemd.

This isn't a command that I would normally do. It's either add a nuke command or have to manually look up the process id and kill that. You can imagine my preference. =)

Thanks again.

berndbausch · 11-18-2015, 05:30 PM

Quote:

Originally Posted by Quakeboy02

This isn't a command that I would normally do. It's either add a nuke command or have to manually look up the process id and kill that. You can imagine my preference. =)

Well the question is how to properly addmthe nuke command in a systemd context. But anyway, good luck!

Quakeboy02 · 11-18-2015, 05:35 PM

Yeah, I know that. But I've got enough to fill my plate without wondering why this init.d script thinks that the mythlogserver is incapable of failing. So, since nuke works... =)