When an exit from the frontend is requested it will never shut down. On the usual shutting down screen at the top it says:
Code: Select all
mythtv is in a daily wakeup/shutdown period ...
Code: Select all
mythshutdown -x
In a daily wakeup period (1).
Not OK to shutdown
I looked around in the log files and didn't find "period" at all, or anything that looked like a problem for "wakeup". Also, I don't even know what a "daily wakeup/shutdown" means. Up/down are set by whatever will be recorded, and those are whenever, so there are days where nothing would record and the box would never come up (or down.) Here are the last few messages relating to "shutdown" in mythbackend.log
Code: Select all
mythbackend.log:Feb 19 13:24:59 mediahog mythbackend: mythbackend[1308]: N Scheduler scheduler.cpp:3123 (HandleIdleShutdown) Client is connected, removing startup block on shutdown
mythbackend.log:Feb 19 13:30:14 mediahog mythbackend: mythbackend[1308]: N Scheduler scheduler.cpp:3292 (HandleIdleShutdown) Blocking shutdown because of a connected client
mythbackend.log:Feb 19 14:46:42 mediahog mythbackend: mythbackend[1521]: N Scheduler scheduler.cpp:3123 (HandleIdleShutdown) Client is connected, removing startup block on shutdown
Using the account that the backend runs in, ran the optimize_mythdb.pl script. Same message, no way out of front end. Rebooted (in case some of these changes need that to "take".) Problem persists. mythfilldabase.log was not modified after this reboot, which might be a clue.
What do I need to kick to get it out of this state? Seems like there is a lock file or flag in the database which is set and needs to be unset.
Thanks.