Author |
Message |
mattbatt
|
Posted: Thu Jul 30, 2015 6:10 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
7 Days of guide data might be the problem. I'm using Schedules direct and I usually have 12 days of guide data. Make sure your subscription hasn't lapsed. Keeping MTC happy seems to be a full time job. God forbid you watch TV during the midnight backup.
_________________ My System
|
|
Top |
|
|
nicom
|
Posted: Thu Jul 30, 2015 11:09 pm |
|
Joined: Mon Aug 14, 2006 8:24 pm
Posts: 320
Location:
Melbourne, Australia
|
tscholl wrote: Does anyone know where "_FRONTEND_,test" being picked up from? I too am looking for what keeps recreating my phantom FE "vm-test" as I am still getting the same error messages. bgrant3406 wrote: if you do a search through Mythconverg you will find table entries for you FE, "test". I searched my mythconverg.sql and found no reference to "vm-test". Does anyone know what keeps looking for phantom frontends?
_________________ Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest
|
|
Top |
|
|
bgrant3406
|
Posted: Fri Jul 31, 2015 5:58 am |
|
Joined: Tue Jul 01, 2014 6:49 am
Posts: 92
|
nicom wrote: bgrant3406 wrote: if you do a search through Mythconverg you will find table entries for you FE, "test". I searched my mythconverg.sql and found no reference to "vm-test". Does anyone know what keeps looking for phantom frontends? Take a look at idle.py, it will show you what LinHES is looking at to determine the idle/busy status of the system prior to running a maintenance item. If you are seeing "vm-test" in your myth_mtc log during an idle check (which runs multiple times during maintenance), that is what is calling it. There are multiple tables that have host info, not all of them will have data populated for a specific host, but settings is normally the one that always will: Code: mysql> SELECT table_name,table_schema FROM INFORMATION_SCHEMA.COLUMNS WHERE column_name="hostname"; +----------------------------+--------------+ | table_name | table_schema | +----------------------------+--------------+ | capturecard | mythconverg | | displayprofilegroups | mythconverg | | housekeeping | mythconverg | | inuseprograms | mythconverg | | jobqueue | mythconverg | | jumppoints | mythconverg | | keybindings | mythconverg | | keybindings_distro_default | mythconverg | | music_playlists | mythconverg | | profilegroups | mythconverg | | recorded | mythconverg | | recordedfile | mythconverg | | scannerpath | mythconverg | | settings | mythconverg | | settings_distro_default | mythconverg | | storagegroup | mythconverg | | weatherscreens | mythconverg | | weathersourcesettings | mythconverg | +----------------------------+--------------+ From what I can see Idle.py is looking for available front ends by checking for FrontendIdleTimeout in the settings table, when I look at my DB I see the following: Code: mysql> select * from settings where value = "FrontendIdleTimeout"; +---------------------+------+--------------------------------+ | value | data | hostname | +---------------------+------+--------------------------------+ | FrontendIdleTimeout | 90 | macbook-air.local | | FrontendIdleTimeout | 0 | air.home | | FrontendIdleTimeout | 90 | gbr_fe | | FrontendIdleTimeout | 0 | gbr_sbe | | FrontendIdleTimeout | 0 | mbe | | FrontendIdleTimeout | 0 | mbr_sbe | | FrontendIdleTimeout | 0 | mediaroom_sbe | +---------------------+------+--------------------------------+ 7 rows in set (0.00 sec) As a note, the two items that have data = 90 are my phantoms, the first one due to Apple changing the way that devices ID themselves, the gbr_fe was a test box I had setup at one point. HTH.
|
|
Top |
|
|
bgrant3406
|
Posted: Fri Jul 31, 2015 6:10 am |
|
Joined: Tue Jul 01, 2014 6:49 am
Posts: 92
|
mattbatt wrote: God forbid you watch TV during the midnight backup. The cool thing about idle.py is that as soon as the check finds anything going on, maintenance is postponed and nothing happens other than idle.py is rescheduled to check again in 10 minutes. Based on that, sometimes an FE will show red while the others are green, this can be caused by not being in a menu screen, idle.py thinks your system is busy and won't run. So if you see a specific front end (assuming multiple FE in your setup) that shows red for myth_mtc, the likely culprit is that it is not displaying a menu. To see if this is the item, escape out to the main menu, wait 20 minutes and see if myth_mtc for that FE is now green. Alternately check your myth_mtc log for that FE and see what it has to say about idle or not.
|
|
Top |
|
|
mattbatt
|
Posted: Fri Jul 31, 2015 9:32 am |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
bgrant3406 wrote: mattbatt wrote: God forbid you watch TV during the midnight backup. The cool thing about idle.py is that as soon as the check finds anything going on, maintenance is postponed and nothing happens other than idle.py is rescheduled to check again in 10 minutes. Based on that, sometimes an FE will show red while the others are green, this can be caused by not being in a menu screen, idle.py thinks your system is busy and won't run. So if you see a specific front end (assuming multiple FE in your setup) that shows red for myth_mtc, the likely culprit is that it is not displaying a menu. To see if this is the item, escape out to the main menu, wait 20 minutes and see if myth_mtc for that FE is now green. Alternately check your myth_mtc log for that FE and see what it has to say about idle or not. Yeah it eventually runs when it can. I had MTC giving me red for another reason and I had to slog through all the "busy" entries in the log before I could find what was really causing the issue. Also The extra Frontends are in your database and when I asked about removing my old FEs the general response was "they aren't hurting anything and you could screw something up if you go mucking about in the Database" Mine aren't causing any issues so i doubt yours are. Code: 2015-07-31T00:36:02.023100-04:00 gimli myth_mtc: 2015-07-31T00:36:03.353916-04:00 gimli myth_mtc: 2015-07-31T00:36:03.353932-04:00 gimli myth_mtc: 2015-07-31 00:36 2015-07-31T00:36:03.415933-04:00 gimli myth_mtc: Checking system idle... 2015-07-31T00:36:03.533828-04:00 gimli myth_mtc: Checking if the schema is locked... 2015-07-31T00:36:03.534107-04:00 gimli myth_mtc: The schema is NOT locked. 2015-07-31T00:36:03.534117-04:00 gimli myth_mtc: Checking if programs are in use... 2015-07-31T00:36:03.534413-04:00 gimli myth_mtc: Programs are NOT in use. 2015-07-31T00:36:03.534423-04:00 gimli myth_mtc: Checking jobqueue for active jobs... 2015-07-31T00:36:03.534569-04:00 gimli myth_mtc: No jobs are active. 2015-07-31T00:36:03.534578-04:00 gimli myth_mtc: Checking if mythfilldatabase is running... 2015-07-31T00:36:03.548281-04:00 gimli myth_mtc: mythfilldatabase is NOT running. 2015-07-31T00:36:03.548308-04:00 gimli myth_mtc: Checking if mythtv-setup is running... 2015-07-31T00:36:03.558092-04:00 gimli myth_mtc: mythtv-setup is NOT running. 2015-07-31T00:36:03.558111-04:00 gimli myth_mtc: Checking for recordings in the next 15 minutes... 2015-07-31T00:36:03.667405-04:00 gimli myth_mtc: No recordings starting in 15 minutes. 2015-07-31T00:36:03.668399-04:00 gimli myth_mtc: Checking for playing mythfrontends... 2015-07-31T00:36:03.669614-04:00 gimli myth_mtc: Checking frodo's mythfrontend status... 2015-07-31T00:36:04.537652-04:00 gimli myth_mtc: Could not connect to frodo's mythfrontend. 2015-07-31T00:36:04.537689-04:00 gimli myth_mtc: Checking galadmyth's mythfrontend status... 2015-07-31T00:36:05.314450-04:00 gimli myth_mtc: Could not connect to galadmyth's mythfrontend. 2015-07-31T00:36:05.314487-04:00 gimli myth_mtc: Checking galadriel's mythfrontend status... 2015-07-31T00:36:06.420504-04:00 gimli myth_mtc: Could not connect to galadriel's mythfrontend. 2015-07-31T00:36:06.420540-04:00 gimli myth_mtc: Checking gimli's mythfrontend status... 2015-07-31T00:36:06.505563-04:00 gimli myth_mtc: gimli's mythfrontend is in StandbyMode. 2015-07-31T00:36:06.505586-04:00 gimli myth_mtc: System is idle. 2015-07-31T00:36:06.525845-04:00 gimli myth_mtc: 2015-07-31T00:36:06.525862-04:00 gimli myth_mtc: ####################################### 2015-07-31T00:36:06.526071-04:00 gimli myth_mtc: 2015-07-31T00:36:06.526077-04:00 gimli myth_mtc: 2015-07-31 00:36 Running Optimize
_________________ My System
|
|
Top |
|
|
tscholl
|
Posted: Fri Jul 31, 2015 9:38 am |
|
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location:
Lexington, Ky
|
Matt, Yea, but in my case the script runs, with no errors and always posts that the script did not run. A copy of a typical log can be found here. Don't know why it thinks it never competed? Perplexed .
|
|
Top |
|
|
brfransen
|
Posted: Fri Jul 31, 2015 12:11 pm |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
Tim,
What is your hostname? What is the path to the log file in Health & Maintenance and is that the log file you posted?
|
|
Top |
|
|
amtrakuk
|
Posted: Fri Jul 31, 2015 2:54 pm |
|
Joined: Thu Jul 30, 2015 10:00 am
Posts: 35
|
mattbatt wrote: 7 Days of guide data might be the problem. I'm using Schedules direct and I usually have 12 days of guide data. Make sure your subscription hasn't lapsed. Keeping MTC happy seems to be a full time job. God forbid you watch TV during the midnight backup. I'm using the EIT data for Freeview UK - its only 7 days, although only 7 days it keeps the box busy recording
|
|
Top |
|
|
nicom
|
Posted: Fri Jul 31, 2015 6:50 pm |
|
Joined: Mon Aug 14, 2006 8:24 pm
Posts: 320
Location:
Melbourne, Australia
|
This thread has been most informative for me. mattbatt wrote: Also The extra Frontends are in your database and when I asked about removing my old FEs the general response was "they aren't hurting anything and you could screw something up if you go mucking about in the Database" Mine aren't causing any issues so i doubt yours are. The problem I have is that the name of my phantom causes an error due to the presence of a hyphen. Code: Error: /home/xymon/server/etc/mythdot: syntax error in line 6 near '-' The funny thing is that I only get Condition Red intermittently, which perhaps indicates that it is not due to the error and perhaps due to lack of idleness. Looking at the history of myth_mtc on the web page I see I have Condition Red about every second day for durations of less than 1 day but sometimes 2 days. One other thing is my machine wakes on ACPI and shuts down when not needed so it doesn't spend much time being idle. Maybe I need to increase that. bgrant3406 wrote: if you do a search through Mythconverg you will find table entries for you FE, "test".
When I do the proper search of mythconverg as you suggest (not just grep) I see it. Code: mysql> select * from settings where value = "FrontendIdleTimeout"; +---------------------+------+-------------+ | value | data | hostname | +---------------------+------+-------------+ | FrontendIdleTimeout | 90 | silverstone | | FrontendIdleTimeout | 90 | vm-test | +---------------------+------+-------------+ 2 rows in set (0.00 sec)
_________________ Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest
|
|
Top |
|
|
mattbatt
|
Posted: Sat Aug 01, 2015 12:20 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
tscholl wrote: Matt, Yea, but in my case the script runs, with no errors and always posts that the script did not run. A copy of a typical log can be found here. Don't know why it thinks it never competed? Perplexed . I admit this is a stupid question but...... are you looking in the directory for the correct day that MTC fails? If it's erroring some days you might have pulled the log from a day when it didn't error. You are right I don't see a reason why that log would have errored.
_________________ My System
|
|
Top |
|
|
tscholl
|
Posted: Sat Aug 01, 2015 8:05 pm |
|
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location:
Lexington, Ky
|
The full path to the log that was posted was /var/log/2015-07-16 But of course that subdir no longer exists. When I look at mtc in xymon here's what is says today Code: Sat Aug 01 21:50:31 EDT 2015
** Maintenance script did not run. ** BACKUP FILE WAS NOT CREATED The system may have been busy Log file: /var/log/2015-08-01/myth_mtc.log
12 days of guide data
No remote backup jobs queued Status unchanged in 40 days, 6 hours, 8 minutes Status message received from 127.0.0.1 And here is the /var/log/2015-08-01/myth_mtc.logOn July 16, my first post Code: myth_mtc on mythtv RED for 23 days, 17 hours, 36 minutes, 49 seconds My machines name is mythtv which matches to MBEwFW _MASTERFRONTEND_,mythtv Also I deleted test which matched _FRONTEND_,test from the database and it no longer shows up in the latest log.
|
|
Top |
|
|
brfransen
|
Posted: Sun Aug 02, 2015 2:15 pm |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
That is odd. The file name should be mythtv_myth_mtc.log. From terminal what does hostname give you?
|
|
Top |
|
|
tscholl
|
Posted: Sun Aug 02, 2015 2:25 pm |
|
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location:
Lexington, Ky
|
I think you've figured out the problem. command line says root@mythtv etc/hosts says 192.168.20.52 mythtv If it's looking for a file named /var/log/2015-08-01/myth_mtc.log It that says' /var/log/2015-08-01/mythtv_myth_mtc.log I'd say the a good reason it doesn't think it ran. Good catch!! Here is my complete list of my log names. Code: mythtv_cron.log -rw-r--r-- 1 root root 580 Aug 2 18:28 mythtv_dbus.log -rw-r--r-- 1 root root 122195 Aug 2 18:28 mythtv_frontend.log -rw-r--r-- 1 root root 1556 Aug 2 15:53 mythtv_irsend.log -rw-r--r-- 1 root root 3264 Aug 2 15:53 mythtv_kernel.log -rw-r--r-- 1 root root 148418 Aug 2 18:28 mythtv_lighttpd.log -rw-r--r-- 1 root root 2316 Aug 2 15:53 mythtv_lircd-0.9.2a.log -rw-r--r-- 1 root root 31720 Aug 2 18:20 mythtv_maillog.log -rw-r--r-- 1 root root 148703 Aug 2 18:28 mythtv_messages.log -rw-r--r-- 1 root root 346286 Aug 2 18:28 mythtv_mythbackend.log -rw-r--r-- 1 root root 19627 Aug 2 17:03 mythtv_mythcommflag.log -rw-r--r-- 1 root root 128878 Aug 2 18:28 mythtv_mythfrontend.log -rw-r--r-- 1 root root 19008 Aug 2 17:01 mythtv_mythmetadatalookup.log -rw-r--r-- 1 root root 38825 Aug 2 00:30 mythtv_myth_mtc.log -rw-r--r-- 1 root root 94465 Aug 2 17:45 mythtv_mythpreviewgen.log -rw-r--r-- 1 root root 127 Aug 2 13:31 mythtv_php.log -rw-r--r-- 1 root root 1219 Aug 2 18:28 mythtv_sshd.log -rw-r--r-- 1 root root 5556 Aug 2 18:23 mythtv_su.log
|
|
Top |
|
|
nicom
|
Posted: Sun Aug 02, 2015 6:25 pm |
|
Joined: Mon Aug 14, 2006 8:24 pm
Posts: 320
Location:
Melbourne, Australia
|
tscholl wrote: Also I deleted test which matched _FRONTEND_,test from the database and it no longer shows up in the latest log. Can you tell me how you did that. I would like to exorcise of my phantom as well and my knowledge of sql is abysmal.
_________________ Intel DG965WH, Dvico DVB-T Lite x2, HDHR, Gigabyte GT220, KingstonSSD, WD20EARS version=latest
|
|
Top |
|
|
brfransen
|
Posted: Sun Aug 02, 2015 6:27 pm |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
What does the actual cmd give: Code: hostname
|
|
Top |
|
|