<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head><body style="">
<div>
<div style="font-family: -moz-fixed; font-size: 12px;" class="moz-text-flowed" lang="x-western">
I recently updated my arch system which is running my dedicated backend/remote frontend setup. This pulled in 0.26 and the arch change to systemd, amongst other things.
<br/>Since then automatic shutdown of the backend is no longer working.
<br/>
<br/>I think I have established a pattern and believe the problem is related to scheduler.cpp, but I have no idea how to fix this.
<br/>
<br/>Scenario 1:
<br/>
<br/>- Boot backend
<br/>
<br/>- do nothing else (e.g. start remote frontend or mythfrontend on the backend)
<br/>
<br/>- automatic shutdown does not work
<br/>
<br/>Scenario 2:
<br/>
<br/>- Boot backend
<br/>
<br/>- start remote frontend
<br/>
<br/>- shut down frontend
<br/>
<br/>- automatic shutdown does not work
<br/>
<br/>- restart backend service (without reboot)
<br/>
<br/>- automatic shutdown works
<br/>
<br/>I also notice that in scenario 2 (when automatic shutdown works) there are a whole heap of these kind of messages right until shutdown occurs:
<br/>
<br/>2013-04-29  19:18:07.592125  N[660/738]  Expire  autoexpire.cpp:641  (SendDeleteMessages)  -  Expiring  156  MBfor  1073  at2013-04-13T11:50:20Z  =>  Hulk
<br/>2013-04-29  19:18:07.632899  E[660/660]  CoreContext  mainserver.cpp:2610  (DoHandleDeleteRecording)  -  ERRORwhen  trying todelete  file:  myth://192.168.1.103:65103:6543/1070_20120126203445.mpg. File doesn't exist.  Database metadata will not be removed.
<br/>2013-04-29  19:18:07.889638  E[660/660]  CoreContext  mainserver.cpp:2610  (DoHandleDeleteRecording)  -  ERRORwhen  trying todelete  file:  myth://192.168.1.103:65103:6543/1022_20120206192600.mpg. File doesn't exist.  Database metadata will not be removed.
<br/>
<br/>I am starting to think this has to do with scheduler.cpp
<br/>
<br/>In scenario 2 (successful) I see the following in the log just before the above auto expire stuff:
<br/>
<br/>Scheduler  scheduler.cpp:2307  (HandleRunSchedulerStartup)  -  Scheduler:  Seem  to be woken upby  USER
<br/>
<br/>then a whole heap of auto expiry stuff and finally:
<br/>
<br/>Scheduler  scheduler.cpp:2862  (CheckShutdownServer)  -  CheckShutdownServer  returned-  OK to shutdown
<br/>2013-04-29  19:19:55.276775  N[660/735]  Scheduler  scheduler.cpp:2947  (ShutdownServer)  -  Running  the command toset  thenext  scheduled wakeup time:-
<br/>                                                sudo/home/laffi/scripts/MythSetWakeup  1367229120
<br/>2013-04-29  19:19:55.372582  N[660/735]  Scheduler  scheduler.cpp:2974  (ShutdownServer)  -  Running  the command to shutdownthis  computer:-
<br/>                                                sudo/home/laffi/scripts/MythShutdown
<br/>
<br/>In scenario 1 (unsuccessfull shutdown) I also get
<br/>
<br/>Scheduler  scheduler.cpp:2307  (HandleRunSchedulerStartup)  -  Scheduler:  Seem  to be woken upby  USER
<br/>
<br/>and then autoexpiry, but then, once a frontend connects:
<br/>
<br/>ProcessRequest  mainserver.cpp:1385  (HandleAnnounce)  -  adding:  frontendas  a client(events:  0)
<br/>
<br/>I don't get autoexpiry of files and no shutdown, both of which I believe are initiated by scheduler.cpp
<br/>
</div>
</div>
</body></html>