How to check Nightly Maintenance is completing on Mobility server

How to verify if Nightly Maintenance is completing on the Mobility server.

Although there can be many reasons as to why Nightly Maintenance stops or is not completing, the purpose of this TID is to verify Nightly Maintenance is running and finishing on the Mobility server. Troubleshooting steps may depend on unique circumstances of the server. If Nightly Maintenance is not completing successfully, please see TID 7012712 for a potential reason. Otherwise, try increasing the duration of Nightly Maintenance.

Verify Nightly Maintenance is configured, running and finishing properly using dsapp:

1. See TID 7015282  - How to install dsapp on a Mobility server.
   Note: Once dsapp is loaded, proceed with the steps below.
   
   
2. Select Checks & Queries | Nightly Maintenance Check:
   Note: This will check any archived logs dated within the past 5 days.
   
   Nightly Maintenance:
         <databaseMaintenanceStartHour>13</databaseMaintenanceStartHour>
         <databaseMaintenance>1</databaseMaintenance>
         <databaseMaintenanceStopHour>20</databaseMaintenanceStopHour>
         <databaseMaintenanceDeleteDaysInPast>30</databaseMaintenanceDeleteDaysInPast>
   
   Nightly Maintenance History:
   2013-10-14 13:00:10.452 INFO [MaintenanceMonitor_Thread] [maintenanceMonitor:180] [userID:] [eventID:] [objectID:] [MaintenanceMonitor] Nightly maintenance starting removal of orphaned attachments.
   2013-10-14 13:00:14.206 INFO [MaintenanceMonitor_Thread] [maintenanceMonitor:185] [userID:] [eventID:] [objectID:] [MaintenanceMonitor] Nightly maintenance removal of orphaned attachments successful.
   2013-10-14 13:00:14.206 INFO [MaintenanceMonitor_Thread] [maintenanceMonitor:194] [userID:] [eventID:] [objectID:] [MaintenanceMonitor] Nightly maintenance successful for 3 out of 3 users.
   
   
3. The above signifies a successful Nightly Maintenance. If nothing is displayed in the Nightly Maintenance History section, please see below to manually check the archived log for previous days.
   

Note: Nightly Maintenance information is only logged in INFO or DEBUG (not WARN).

How to determine manually:

1. Nightly Maintenance configuration. From a terminal window:
• grep -i maintenance /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/mobility/connector.xml:
  <databaseMaintenanceStartHour>13</databaseMaintenanceStartHour>
  <databaseMaintenance>1</databaseMaintenance>
  <databaseMaintenanceStopHour>20</databaseMaintenanceStopHour>
  <databaseMaintenanceDeleteDaysInPast>30</databaseMaintenanceDeleteDaysInPast>
  
  
  
2. Nightly Maintenance running and finishing. From a terminal window:
   
   • cd /var/log/datasync/connectors/
   • grep -i "Nightly maintenance" mobility-agent.log:
     Note: If using DataSync 1.2.5 or older, replace mobility-agent.log with default.pipeline1.mobility-AppInterface.log.
     
• 2013-08-30 13:00:16.412 INFO [MaintenanceMonitor_Thread] [maintenanceMonitor:194] [userID:] [eventID:] [objectID:] [MaintenanceMonitor] Nightly maintenance successful for 4 out of 4 users.
• Nightly maintenance successful for # out of # users.
  
• If nothing is found, check the archived log for the previous day:
• zgrep -i "Nightly maintenance" mobility-agent.log-20130830 (replacing 20130830 with the correct date string corresponding to an existing filename)
  Note: If using DataSync 1.2.5 or older, replace mobility-agent.log with default.pipeline1.mobility-AppInterface.log.
  
• If Nightly Maintenance is not completing successfully, please see TID 7012712.