- Stop Chronicall
- Stop Postgres Database
- Stop and restart all other services
- Start Postgres Database
- Start Chronicall
Windows
If you need to start, stop, or restart Chronicall do the following:
- Open the Start menu and type services.msc into the search bar. A listing for Services should appear at the top of the list, click on it.
- Search through the list to find the appropriate Chronicall services
- For 3.9.4 and below, service names are:
- chronicall
- chronicall database
- chronicall recording library
- For 3.9.5 to 3.12.5, service names have changed to:
- ChronicallServer
- Chronicall Database (Postgres)
- Chronicall Database (OrientDB)
- ChronicallMultimedia
- ChronicallRecordingLibrary
- For 4.0 and above, service names have changed to:
- ChronicallServer
- ChronicallMultimedia
- ChronicallRecordingLibrary
- For 3.9.4 and below, service names are:
- Right-click on the related service and choose Start, Stop, or Restart to change its status.
Linux
To start, stop, or restart Chronicall on a Linux device, use the following commands (each service may require root permissions). "Restart" is equivalent to a "Stop" and "Start."
For versions 3.8.7 and earlier, service names are as follows:
- Chronicall
- service chronicall start
- service chronicall stop
- service chronicall restart
- Chronicall Database
- service chronicall_database start
- service chronicall_database stop
- service chronicall_database restart
- Chronicall Recording Library
- service recording_library start
- service recording_library stop
- service recording_library restart
- Orient Database
- service chronicall_cdr_database start
- service chronicall_cdr_database stop
- service chronicall_cdr_database restart
- Recording Library
- service ChronicallRecordingLibrary start
- service ChronicallRecordingLibrary stop
- service ChronicallRecordingLibrary restart
- Multimedia
- service ChronicallMultimedia start
- service ChronicallMultimedia stop
- service ChronicallMultimedia restart
For 3.9.5 to 3.12.5, service names have changed to:
- service ChronicallServer start
- service ChronicallDatabaseOrientDB start
- service ChronicallDatabasePostgres start
- service ChronicallRecordingLibrary start
- service ChronicallMultimedia start
For 4.0 and above, service names have changed to:
- service ChronicallServer start
- service ChronicallRecordingLibrary start
- service ChronicallMultimedia start
In rare instances, you may need to go into the following directories to manually restart services using startup.sh, shutdown.sh or restart.sh:
- Chronicall
- Earlier than 3.9.5: /var/lib/Xima\ Software/Chronicall/tomcat/bin
- 3.9.5 or later: /var/lib/chronicall/bin/
- Postgres
- Earlier than 3.9.5: /var/lib/Xima\ Software/Chronicall/postgres/bin
- 3.9.5 or later: /var/lib/chronicall/postgres/bin/
- OrientDB
- Earlier than 3.9.5: /var/lib/Xima\ Software/Chronicall/orientdb/\bin
- 3.9.5 or later: /var/lib/chronicall/orientdb/bin/
- Recording Library
- Earlier than 3.9.5: /var/lib/Xima\ Software/Chronicall/recording\ library/bin
- 3.9.5 or later: /var/lib/chronicall/recording\ library/bin/
Other bin directories will have these for other services as well. Manually restarting the Chronicall service here would look like this:
./restart.sh
It is usually not necessary to restart the Chronicall Database or Chronicall Recording Library services unless you are migrating Chronicall to a new server.
- For more information, see our migration articles: Chronicall Server Migration - 3.9.4 and Earlier & Chronicall Server Migration 3.10 and Up.
While the Chronicall service is stopped, it will not log any calls. It is recommended to perform Java updates and migrating servers during low call volume hours or after hours. Be sure to restart each service when you are finished.
Related Troubleshooting Workflows
This article is useful in the following Troubleshooting Workflows:
Troubleshooting Flow
Overview → Are Services Running? → Unregistered Serial Error→Verify Connection Settings