1. Error "Unable to schedule backup in /path/to/dir" in LMS 3.1. However, immediate backup is fine. Is this because cron access is disabled to all users? Any workaround to the lack of cron?
2. After importing LMS 2.6 backup in LMS 3.1, a number of phantom devices (some from the past) showed up in DCR and RME. Are they never deleted from the DB (crud from LMS 2.2 and before)?
3. After a hostname change on the LMS 3.1 server, syslog collector status shows both the old and new hostnames in FQDN form, status N/A across the board. Adding new hostname (sans the dot com part) gets it collecting, but the old hostname.fqdn.com refuses to be removed.
After restarting syslogcollector and sysloganalyzer processes, the orignal old/new hostnames.fqdn.com entries return, and both shows N/A across the board again. The "new-hostname.fqdn.com" entry can be unsubscribed, the "old-hostname.fqdn.com" cannot.
/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/Subscribers.dat looks ok, so where is old-hostname stored?
Somehow I apparently have debug on, but I'm not seeing any clue what's wrong with syslogcollector.
Can I solve the problem by deleting the two *3333 directories in /opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/?
4. I'm 90% sure whatever causes restorebackup.pl to leave a copy of IPMDB.db in / also gets /var and /var/adm owned by casuser:casusers, which would cause problem for other apps. Is this a known issue?