View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 1 post ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Wed Jan 27, 2010 12:03 pm 
Offline
Joined: Thu Apr 03, 2008 11:42 pm
Posts: 114
Location: Calgary, Canada
I'm having an issue where the frontend and some of my daemons are failing to connect to the backend after a reboot because the backend is slow to come up. It does not happen all the time, maybe 50%. Example:

frontend:
Code:
2009-12-27 18:31:31.784 MythContext: Connecting to backend server: 192.168.0.3:6543 (try 1 of 1)
2009-12-27 18:31:31.786 Connection to master server timed out.
                        Either the server is down or the master server settings
                        in mythtv-settings does not contain the proper IP address

backend (note 3 seconds later):
Code:
2009-12-27 18:31:34.198 mythbackend version: branches/release-0-22-fixes [22957]
 www.mythtv.org
2009-12-27 18:31:34.204 Using runtime prefix = /usr

This has been going on for a while, since I upgraded to the -22000 release of 0.22 in -testing from what I can tell. I didn't worry about it initially because I thought it was just the frontend... just found out about the background processes recently.

How can I prioritize the backend so it starts first and finishes starting before the frontend and others go? I'm not familiar enough with runsv to even know where to start.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 1 post ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 31 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu