hangs after myth setup

[archived]

Hello,

After I go through mythtv's setup it hangs on please wait while your application is launched. And it will stay that way for over an hour. Any clues?

Thanks,
Brandon

[archived]

BTW, F4 is a keyboard shortcut that should take you back to the main menu.

RE: Myth...  We have a module call App Server (application server) that is our DCE Device responsible for spawning external applications (like Myth Setup).  My guess is the Myth TV backend crashed or something.  That's not all that infrequent, although since we upgraded to Myth .18 a couple weeks ago it's been much better.

To watch App Server's log and see what myth is doing, if you're a Linux guy you can login and cd /var/log/pluto, then ls *App* to find the log, and tail -f the .newlog file.  

If you're not a Linux user, go into Pluto Admin, choose advanced, devices, locate the media director.  If it's a hybrid, it will be called "Core/Hybrid" as a child of the CORE, otherwise it will be it's own top level device.  Expand that node and directly under the media director will be the app server device.  (NOTE: If you have a hybrid, which is a combination core + m/d, the core will have it's own AppServer too--you want the media directors).

When you click on the device, you will see it's advanced properties and a link for "Follow log".  That will launch a popup that monitors the log.  Now try to run Myth Setup, then post back here what's in the log.

Also, I'm assuming you first tried doing a clean reboot?  Here is what AppServer's log looks like on my machine when I hit Myth Setup:

10   06/19/05 10:04:45.443      Connect OK
10   06/19/05 10:06:42.196      Receive string: MESSAGE 196          
10   06/19/05 10:06:42.196      SpawnApp file: /bin/bash name MythTvSetup args -c   /usr/pluto/bin/launchMythSetup.sh failure 0 19864 1 4 16 3251.0.0 logo 1
10   06/19/05 10:06:42.196      The 'application spawning' background is running!. Telling the orbiter to select the application!
10   06/19/05 10:06:42.196      InternalSendCommand confirmation conf 1 resp (nil)
10   06/19/05 10:06:42.229      InternalSendCommand confirmation done conf 1 resp (nil) (1) OK
ProcessUtils::SpawnApplication() sCMDExec /bin/bash parms: -c   /usr/pluto/bin/launchMythSetup.sh size: 36
dupped exec /bin/bash
dupped arg 0 -c
dupped arg 1 /usr/pluto/bin/launchMythSetup.sh
ProcessUtils::SpawnApplication() Found 3 arguments
ProcessUtils::SpawnApplication() Argument 0: /bin/bash
ProcessUtils::SpawnApplication() Argument 1: -c
ProcessUtils::SpawnApplication() Argument 2: /usr/pluto/bin/launchMythSetup.sh
Freed args
ProcessUtils::SpawnApplication() adding this 16001 pid to the spawned list for MythTvSetup
05   06/19/05 10:06:42.234      Finished spawning 'MythTvSetup': /bin/bash -c   /usr/pluto/bin/launchMythSetup.sh.

If you know Linux, you can also look in /var/log/pluto for the pid (ls *16001* in my case) and see if there's a log for that.

You can also do a process list to see what's running.  I've got a core/hybrid here and when I do: ps aux | grep -i myth   here's what I get:
root     13029  0.0  0.2  2668 1204 ?        Ss   10:04   0:00 SCREEN -d -m -S MythTV_Backend_Proxy-19858 /usr/pluto/bin/Spawn_Device.sh 19858 localhost MythTV_Backend_Proxy
root     13030  0.0  0.2  2396 1160 pts/8    Ss+  10:04   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 19858 localhost MythTV_Backend_Proxy
root     13453  0.0  0.4 28824 2356 pts/8    S+   10:04   0:00 ./MythTV_Backend_Proxy -d 19858 -r localhost
root     13454  0.0  0.2  2396 1064 pts/8    S+   10:04   0:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 19858 localhost MythTV_Backend_Proxy
root     13455  0.0  0.0  1496  348 pts/8    S+   10:04   0:00 tee /var/log/pluto/19858_MythTV_Backend_Proxy.newlog
root     14085  0.0  0.2  2800 1404 ?        Ss   10:04   0:00 SCREEN -d -m -h 3000 -S 19866_MythTV_Player /bin/bash -x Spawn_Device.sh 19866 localhost MythTV_Player
root     14086  0.0  0.2  2392 1184 pts/20   Ss+  10:04   0:00 /bin/bash -x Spawn_Device.sh 19866 localhost MythTV_Player
root     14365  0.0  0.5 21536 2660 pts/20   S+   10:04   0:00 ./MythTV_Player -d 19866 -r localhost
root     14366  0.0  0.2  2392 1184 pts/20   S+   10:04   0:00 /bin/bash -x Spawn_Device.sh 19866 localhost MythTV_Player
root     14367  0.0  0.0  1496  404 pts/20   S+   10:04   0:00 tee /var/log/pluto/19866_MythTV_Player.newlog
root     14436  1.3  9.4 91324 48500 pts/20  S+   10:04   0:04 /usr/bin/mythfrontend
mythtv   14605  0.0  2.1 112544 11220 ?      Ss   10:05   0:00 /usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythtv/mythbackend.pid
root     16001  0.0  0.2  2288 1036 pts/10   S+   10:06   0:00 /bin/bash /usr/pluto/bin/launchMythSetup.sh
root     16004  0.3  2.5 47928 13284 pts/10  S+   10:06   0:00 mythtv-setup
root     17588  0.0  0.1  1836  612 pts/23   R+   10:10   0:00 grep -i myth

[archived]

Deleted the original settings in mythtv from the MD, so i could run through a fresh myth setup again. On my other pc I went to pluto-admin site to the follow log as described. There may be a problem...

Follow log
Device App Server, # 28924  
Device template App Server, category App Server and manufacturer Pluto.  
   
Log not found: /var/log/pluto/28924_App_Server.newlog  

I also noticed when MD first boots up in the top right screen after ratpoison, it says no managed windows and then select: unknown window "mythfrontend"

Brandon

[archived]

I also noticed during the process of my core booting, when it gets to starting mythtvserver: mythbackendQsetting error creating ./qt
this doesn't happen during MD's boot.

Thanks,
Brandon

[archived]

This could be related to a problem that we fixed in SVN last week. A new version should be released in the following days.