View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 5 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sun Nov 02, 2014 8:08 am 
Offline
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 425
Location: Charlotte, NC
I have been watching this issue since I upgraded to 8.2 five days ago. The logs keeps repeating the same thing (it actually looks fine to me) but says the system is busy...

Code:
2014-11-02 09:01
Checking system idle...
    Checking if the schema is locked...
        The schema is NOT locked.
    Checking if programs are in use...
        Programs are NOT in use.
    Checking jobqueue for active jobs...
        No jobs are active.
    Checking if mythfilldatabase is running...
        mythfilldatabase is NOT running.
    Checking if mythtv-setup is running...
        mythtv-setup is NOT running.
    Checking for recordings in the next 15 minutes...
        No recordings starting in 15 minutes.
    Checking for playing mythfrontends...
        Checking mythserv's mythfrontend status...
            mythserv's mythfrontend is NOT playing.
            mythserv's mythfrontend is NOT in menus.
System is busy.

2014-11-02 09:01 Waiting 10 minutes before trying again.


Does this mean the maintenance script is not completing or is there some other problem? All other logs are clean and the system seems to be running fine...

_________________
Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.6.1


Top
 Profile  
 
PostPosted: Sun Nov 02, 2014 9:23 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
The maintenance script uses idle.py to see if the system is idle. idle.py is finding that mythserv's mythfrontend is NOT in menus which is why it is saying the system is busy. If a mythfrontend is not in menus that means it is in recordings/videos/music/gallery/etc so idle.py classifies that as busy.


Top
 Profile  
 
PostPosted: Sun Nov 02, 2014 9:30 am 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
A simple way to test is start the PC up. Normally the frontend starts up automatically. Leave it alone, then with google-chrome browse the web for 20 minutes. It should run automatically and mythweb health will change back to green....


Top
 Profile  
 
PostPosted: Sun Nov 02, 2014 10:08 am 
Offline
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 425
Location: Charlotte, NC
OK, I just learned something... All frontend machines (not just the master) must either be off or in menus for this to work otherwise idle.py reports system busy... We leave remote frontend machines in different states...

I don't remember this being the case in 7.4 or in 8.1.1... My wife usually leaves the system in 'watch recordings' and xymon was always green...

_________________
Backend server - 4.0 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.6.1


Top
 Profile  
 
PostPosted: Sun Nov 02, 2014 10:16 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
This was a change with R8.2 specifically with the creation of idle.py. Previously there was idle.sh and the mtc script did it's own checks for idleness. idle.py consolidates the idle checking and is more extensive than the mtc script was in checking idleness.


Top
 Profile  
 

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


All times are UTC - 6 hours




Who is online

Users browsing this forum: Google [Bot] and 28 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