LinHES Forums
http://forum.linhes.org/

Maintenance did NOT complete sucessfully.
http://forum.linhes.org/viewtopic.php?f=21&t=24173		 Page 1 of 3
Author:  nicom [ Sun May 03, 2015 5:14 pm ]
Post subject:  Maintenance did NOT complete sucessfully.
Since upgrading to 8.2 the myth_mtc status on Health & Maintenance has always been red. I can see no obvious errors in the myth_mtc.log and the 2 backups are being created. The only possible thing is it is looking for a frontend (vm-test) which I created a while ago be no longer exists. It seems to object to the hyphen.
How can I stop it looking for this machine?
Any other suggestions to get this back green again?

The following is the last bit of the latest myth_mtc.log
Code:
2015-05-04_08-42/pki/certmaster/ca/certmaster.key
2015-05-04_08-42/pki/certmaster/ca/serial.txt
2015-05-04_08-42/pki/certmaster/ca/certmaster.crt
2015-05-04_08-42/pki/certmaster/silverstone.csr
2015-05-04_08-42/pki/certmaster/silverstone.cert
2015-05-04_08-42/home_dir.tar.gz
Warning: /home/xymon/server/etc/mythdot:6: syntax error in line 6 near '-'
FE _FRONTEND_
MBE _MASTERBACKEND_
MBEwFW _MASTERFRONTEND_,silverstone,vm-test
SLAVEwFW _SLAVEFE_
SLAVE _SLAVEBACKEND_
STD _STANDALONE_

Created file:
    /data/storage/disk0/backup/system_backups/backup.2015-05-04_08-42.tgz

Updating menu with:
    Last backup completed 05/04/15 8:44 AM

Remote backup
    Remote backup is not enabled, copying backup to /data/storage/disk1 if it exists
    Copying system backups to /data/storage/WDCWD20EARS-00MVWB0_WD-WMAZA1408248/backup

#######################################

2015-05-04 08:44 Running System Update
Starting Update

Updating NO packages

#######################################
Finished 2015-05-04 08:42
Author:  nicom [ Sat May 09, 2015 7:29 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
I tried copying an backup version (8.1) of /home/xymon/server/etc/mythdot but the next time myth_mtc ran it overwrote it with the reference to vm-test. Looking at /etc/hosts it only refers to silverstone (my hostname) and localhost so I don't know what is telling it to look for vm-test.

Also I notice that /home/xymon/var/hostdata/silverstone/ has hundreds of files and growing regularly since I installed 8.1. Is this normal?
Author:  RacerX [ Sun May 10, 2015 7:38 am ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
http://forum.linhes.org/viewtopic.php?f ... &hilit=mtc
Author:  nicom [ Sun May 10, 2015 3:54 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
Thanks for the response. I did see that post but my logs all indicate the system is idle and then proceeds with the rest of the script.
Author:  nicom [ Tue Jun 30, 2015 4:57 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully -SOLVED
Updating to 8.3 seems to have solved the problem
Author:  tscholl [ Thu Jul 02, 2015 9:26 am ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
I am having the same issue, but for me it didn't start until I upgraded from R8.2 to R8.3 Ever since then the Health & Maint is alway red for mtc and reports that
Code:
 Thu Jul 02 10:52:20 EDT 2015
 ** Maintenance script did not run. **
    BACKUP FILE WAS NOT CREATED
   
    The system may have been busy
    Log file: /var/log/2015-07-02/myth_mtc.log 

 12 days of guide data

 No remote backup jobs queued

Yet when you look at the log it always says:
Code:
 ##############################                      #########
2015-07-02T00:22:42.868162-04:00 mythtv myth_mtc:
2015-07-02T00:22:42.868168-04:00 mythtv myth_mtc: 2015-07-02 00:22 Running Backu                      p
2015-07-02T00:22:43.405029-04:00 mythtv myth_mtc:
2015-07-02T00:22:43.405076-04:00 mythtv myth_mtc: Starting Backup
2015-07-02T00:22:43.425513-04:00 mythtv myth_mtc:
2015-07-02T00:22:43.425552-04:00 mythtv myth_mtc: Backup mysql databases
2015-07-02T00:22:43.433566-04:00 mythtv myth_mtc: mysql 5.6.23-3
2015-07-02T00:22:43.434501-04:00 mythtv myth_mtc:     mythconverg  (mythtv datab                      ase)
2015-07-02T00:22:46.405679-04:00 mythtv myth_mtc:     ncid (caller id)
2015-07-02T00:22:46.506321-04:00 mythtv myth_mtc:     users
2015-07-02T00:22:46.955875-04:00 mythtv myth_mtc:     All databases in one file
2015-07-02T00:22:50.680261-04:00 mythtv myth_mtc: Backup saved settings
2015-07-02T00:22:50.703397-04:00 mythtv myth_mtc: Backup etc
2015-07-02T00:22:54.568143-04:00 mythtv myth_mtc: Backup func keys
2015-07-02T00:22:54.639493-04:00 mythtv myth_mtc: Backup home dirs
2015-07-02T00:22:54.699726-04:00 mythtv myth_mtc: tar: Removing leading `/' from                       member names
2015-07-02T00:26:43.258128-04:00 mythtv myth_mtc: Compress backup file
2015-07-02T00:28:34.612133-04:00 mythtv myth_mtc: FE _FRONTEND_,test
2015-07-02T00:28:34.612169-04:00 mythtv myth_mtc: MBE _MASTERBACKEND_
2015-07-02T00:28:34.612175-04:00 mythtv myth_mtc: MBEwFW _MASTERFRONTEND_,mythtv
2015-07-02T00:28:34.612179-04:00 mythtv myth_mtc: SLAVEwFW _SLAVEFE_
2015-07-02T00:28:34.612184-04:00 mythtv myth_mtc: SLAVE _SLAVEBACKEND_
2015-07-02T00:28:34.612189-04:00 mythtv myth_mtc: STD _STANDALONE_
2015-07-02T00:28:34.644344-04:00 mythtv myth_mtc:
2015-07-02T00:28:34.644377-04:00 mythtv myth_mtc: Created backup file:
2015-07-02T00:28:34.644384-04:00 mythtv myth_mtc:     /data/storage/disk0/backup                      /system_backups/backup.2015-07-02_00-22.tgz
2015-07-02T00:28:34.644983-04:00 mythtv myth_mtc:
2015-07-02T00:28:34.656378-04:00 mythtv myth_mtc: Updating menu with:
2015-07-02T00:28:34.656411-04:00 mythtv myth_mtc:     Last backup completed 07/0                      2/15 12:28 AM
2015-07-02T00:28:34.733760-04:00 mythtv myth_mtc:
2015-07-02T00:28:34.733802-04:00 mythtv myth_mtc: Remote backup
2015-07-02T00:28:34.733812-04:00 mythtv myth_mtc:     Remote backup is not enabl                      ed, copying backup to /data/storage/disk1 if it exists
2015-07-02T00:28:34.756499-04:00 mythtv myth_mtc:     Link /data/storage/disk1 d                      oesn't exist.
2015-07-02T00:28:35.259094-04:00 mythtv myth_mtc:
2015-07-02T00:28:35.259136-04:00 mythtv myth_mtc: Finished Backup


All of the other maintenance procedures complete normally as well.
The only thing I see that seems a little odd is that the time displayed is always the current system time (within 4 mins or so ) and not the time that the mtc actually ran.
Author:  bgrant3406 [ Thu Jul 02, 2015 9:50 am ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
Interesting on the file name, mine has the master BE/FE (mbe) in the file name, I would have expected yours to look something like mythtv_myth_mtc.log:

Quote:
Thu Jul 02 10:41:58 CDT 2015

Maintenance completed successfully.
Log file: /var/log/2015-07-02/mbe_myth_mtc.log

12 days of guide data

No remote backup jobs queued

Not sure that helps, but may be a lead...

My log file backup section mirrors yours.
Author:  nicom [ Fri Jul 10, 2015 6:02 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
I take it back, the problem is still there. It is still looking for vm-test frontend when it does a backup.
Author:  tscholl [ Thu Jul 16, 2015 10:20 am ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
Does anyone have a solution for this problem? When I ssh into the box I am still getting:
Code:
myth_mtc on mythtv RED for 23 days, 17 hours, 36 minutes, 49 seconds

However I can see no problems in the logs. Latest full log can be found here.

Any thoughts?
Author:  tscholl [ Thu Jul 30, 2015 11:20 am ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
Still having this problem I have noticed one thing. In the list of machines being backed up. Mine reads:
Code:
FE _FRONTEND_,test
MBE _MASTERBACKEND_
MBEwFW _MASTERFRONTEND_,mythtv
SLAVEwFW _SLAVEFE_
SLAVE _SLAVEBACKEND_
STD _STANDALONE_

I think that "_FRONTEND_,test" is what is causing the problem. It did exist at one time but is no longer in service. The only valid machine in the list is "MBEwFW _MASTERFRONTEND_,mythtv"

Does anyone know where "_FRONTEND_,test" being picked up from?
Author:  bgrant3406 [ Thu Jul 30, 2015 12:42 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
if you do a search through Mythconverg you will find table entries for you FE, "test".

I have two "phantom" frontends in my DB and am not seeing any issues with Myth Maint. I did a search on how to remove these phantoms from the database and seemed like more of a hassle than it was worth. For me it was not creating any issues, so easy enough to leave it alone.
Author:  tscholl [ Thu Jul 30, 2015 1:33 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
So your not getting the " Maintenance did NOT complete sucessfully" messages then.
Author:  amtrakuk [ Thu Jul 30, 2015 4:10 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
My installation is new this afternoon and is blinking red.

Code:
 ** Maintenance did NOT complete sucessfully. **
   
    The system may have been busy.
    See the log for more information.
    Log file: /var/log/2015-07-30/mythtv_myth_mtc.log 

 7 days of guide data

 No remote backup jobs queued
Author:  bgrant3406 [ Thu Jul 30, 2015 4:22 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
amtrakuk wrote:
My installation is new this afternoon and is blinking red


The maintenance job tries to run around midnight, if this is a brand new install, the job hasn't run, check again tomorrow to see if you have a problem.
Author:  amtrakuk [ Thu Jul 30, 2015 4:25 pm ]
Post subject:  Re: Maintenance did NOT complete sucessfully.
bgrant3406 wrote:
amtrakuk wrote:
My installation is new this afternoon and is blinking red


The maintenance job tries to run around midnight, if this is a brand new install, the job hasn't run, check again tomorrow to see if you have a problem.


Thanks. Am new to Myth so still getting my head around it ;)
Page 1 of 3 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/