mythbuntu-bugs team mailing list archive

[Oliver Schade <oliver.schade@xxxxxxxxxxxxxx>]

Output of "sudo /usr/bin/mythshutdown -v all -x" (truncated) after the
machine did not shutdown automatically:

[...]
2010-06-17 15:36:38.732 MSqlQuery::exec(DBManager0) SELECT data FROM settings WHERE value = 'mythshutdownwakeuptimefmt' AND hostname = 'mythtv-livingroom' <<<< Returns 1 row(s)
2010-06-17 15:36:38.732 MSqlQuery::next(DBManager0) Result: "data = time_t"
2010-06-17 15:36:38.732 sending command to set time in bios
                        /usr/bin/MythSetWake.sh 1276793010
2010-06-17 15:36:38.736 /usr/bin/MythSetWake.sh 1276793010 exited with code 0
2010-06-17 15:36:38.736 everything looks fine, shutting down ...
2010-06-17 15:36:38.736 MSqlQuery::exec(DBManager1) SELECT data FROM settings WHERE value = 'mythshutdownpoweroff' AND hostname = 'mythtv-livingroom' <<<< Returns 1 row(s)
2010-06-17 15:36:38.736 MSqlQuery::next(DBManager1) Result: "data = sudo /usr/bin/mythshutdown -x"
2010-06-17 15:36:38.736 ..
2010-06-17 15:36:38.736 .
2010-06-17 15:36:38.736 shutting down ...
2010-06-17 15:36:44.991 Got data on select
2010-06-17 15:36:44.991 Processing ready reads
2010-06-17 15:36:44.991 MythSocketThread(sock 0x1f7b8c0:9): socket is readable
2010-06-17 15:36:44.991 MythSocketThread(sock 0x1f7b8c0:9): calling m_cb->readyRead()
2010-06-17 15:36:44.991 MythSocket(1f7b8c0:9): readBlock(0x140072842169784, 8) called
2010-06-17 15:36:44.991 MythSocket(1f7b8c0:9): readBlock(0x140072842168616, 51) called
2010-06-17 15:36:44.991 MythSocket(1f7b8c0:9): read  <-  9 51      BACKEND_MESSAGE[]:[]SHUTDOWN_COUNTDOWN 10[]:[]empty
2010-06-17 15:36:44.991 MythEvent: SHUTDOWN_COUNTDOWN 10
2010-06-17 15:36:44.991 MythSocketThread: Total read time: 0ms, on sockets {9,0ms}
2010-06-17 15:36:44.991 Reacquired ready read lock
2010-06-17 15:36:44.992 ProcessAddRemoveQueues
2010-06-17 15:36:44.992 Construct FD_SET
2010-06-17 15:36:44.992 Waiting on select..
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
sh: /usr/bin/nvram-wakeup: not found
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open

Broadcast message from root@mythtv-livingroom
        (unknown) at 15:36 ...

The system is going down for power off NOW!

--- snip ---

No idea why /usr/bin/nvram-wakeup is being called, it's not in my mythbackend nor in mythwelcome
configuration.

Put the multiple database not open messages are concerning, are they
not?

Thanks, Oliver

-- 
/usr/bin/mythshutdown --shutdown not working
https://bugs.launchpad.net/bugs/594956
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New

Bug description:
Dear Team,


yet another bug on my system - fresh install of 10.04, using mythwelcome on a combined Backend/Frontend.

Once or twice a day mythshutdown is not able to shutdown the system after a recording. mythwelcome, 
shutdown command is set to "sudo /usr/bin/mythshutdown --shutdown".

Manually calling this command on a console results sometimes in the following output:

--- snip ---
os@mythtv-livingroom:~$ sudo /usr/bin/mythshutdown --shutdown
Cannot login to database?

Would you like to configure the database connection now? [no]
[console is not interactive, using default ´no´]
mythshutdown: Could not initialize myth context, Exiting.
--- snip ---

Database and backend use a private IP address (192.168.), not loopback device as the backend serves
other frontends as well. The network cable runs to a switch. Network chipset is a r8149.

I have no idea/clue what this error is about, but it prevents mythwelcome/mythshutdown to shutdown the
system back thus eating power forever.

This error happens only ever 5-8 time - in all other cases mythwelcome shuts down the system as requested.

Any tips?