[mythtv-users] MythTv BE/FE go to sleep but doesn't wake up

Wed Feb 15 20:15:23 UTC 2012

Yes I've set same logging commands.

The today's news is: it is not true that it shutted down around 11:20, but
lost the network connection instead. Now that I'm at now I've checked out
mythbackend.log and syslog and realized that after the startup at 10:30 it *
never* shutted down again:

BTW: here what you asked for:

$ cat mythbackend.log |grep wakeup
2012-02-13 13:45:11.455 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-13T17:25:00
2012-02-13 15:28:15.342 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-13T17:25:00
2012-02-13 19:00:34.554 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-13T19:45:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329158700
2012-02-13 19:12:27.859 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-13T19:45:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329158700
2012-02-13 22:00:26.190 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-13T22:55:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329169500
2012-02-13 22:13:26.497 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-14T00:20:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329175200
2012-02-13 22:24:48.648 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-14T00:20:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329175200
2012-02-14 04:02:26.912 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-14T12:35:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329219000
2012-02-14 14:31:11.973 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-14T15:40:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329230400
2012-02-14 20:50:49.762 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-14T20:55:00
2012-02-14 20:53:51.532 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-14T20:55:00
2012-02-15 00:37:01.332 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-15T12:35:00
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329305400

And let's have a deeper look at the funny thing in the mythbackend.log
(look at the jump from 11:30:57 to 10:31:03)

...
2012-02-15 00:37:01.332 Running the command to set the next scheduled
wakeup time :-
                                                mythshutdown --setwakeup
2012-02-15T12:35:00
2012-02-15 00:37:01.469 Running the command to shutdown this computer :-
                                                mythshutdown --shutdown
Running /usr/bin/setwakeup.sh to set the wakeup time to 1329305400
2012-02-15 11:30:57.756 mythbackend version: fixes/0.24
[v0.24.2-9-g892628e] www.mythtv.org
2012-02-15 10:31:03.334 Using runtime prefix = /usr
2012-02-15 10:31:05.054 Using configuration directory = /home/mythtv/.mythtv
...

The syslog reports the correct timing, instead:

...
Feb 15 00:37:01 multisala init: mythtv-backend main process (1997) killed
by TERM signal
Feb 15 00:37:01 multisala init: tty1 main process (2236) killed by TERM
signal
Feb 15 00:37:01 multisala kernel: Kernel logging (proc) stopped.
Feb 15 11:30:53 multisala kernel: imklog 4.2.0, log source = /proc/kmsg
started.
Feb 15 11:30:53 multisala rsyslogd: [origin software="rsyslogd"
swVersion="4.2.0" x-pid="979" x-info="http://www.rsyslog.com"] (re)start
Feb 15 11:30:53 multisala rsyslogd: rsyslogd's groupid changed to 102
...

Now I'm stopping to think to preserve my mind integrity and get some more
Karma, before continuing to argue something: :)
Let's see what will happen tomorrow

2012/2/15 Douglas Mackay <douglas.mackay at gmail.com>

> On 15 February 2012 16:28, ganassa <ganassa at gmail.com> wrote:
>
> >
> > - the third day, I realized there was some problems. I tried disabling
> NTPD,
> > made some early-tests and then, at 00:41 I let him shut down. I've
> checked
> > the wake-up scheduling - by logging the setwakeup.sh parameter in
> > mythbackend.log (see previous mail) - and it was set up for 12.30.
> Instead,
> > as said, it woke up at 10.30, telling (in the syslog) that it was 11.30,
> and
> > shutdown about 11.20.
> >
> > This thing is getting me mad :)
> >
>
> I'm not sure what extra logging you've added but can you try the
> logging posted here - http://pastebin.com/iUqycEmK
> and then post the relevant lines of your backend log?
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20120215/f8890622/attachment-0001.html 