Check that the required Antidot daemons are running by using the following command:
/usr/local/afs7/bin/antidot status
All Antidot daemons are listed:
- afs-acp.service
- afs-crmanager.service
- afs-entitymanager.service
- afs-host.service
- afs-logmanager.service
- afs-pafmanager.service
- afs-querymanager.service
- afs-stats.service
- afs-updatemanager.service
- bo-ac.service
- bo-analytics.service
- bo-server.service
- cks-alerts.service
- cks-proxy.service
- cks-server.service
The dot at the beginning of each line is green or red:
- Green: the daemon is running
- Red: the daemon is stopped
The PID number is randomly assigned to an operation and does not have to match the documentation.
Ensure that all concerned services are running according to the server role. The following table lists the Antidot daemons expected for every server:
Server role | Daemon |
Indexer | afs-host afs-crmanager afs-pafmanager afs-stats afs-logmanager |
Reply | afs-host afs-querymanager afs-crmanager afs-stats afs-logmanager |
Back Office | afs-host bo-server bo-analytics bo-ac afs-updatemanager afs-stats afs-logmanager |
It is normal if ACP, CKS and the Entity Manager are not running. They are not used in a Fluid Topics environment.
To check why a daemon has stopped, run the following command:
As root user
systemctl status $NAME_OF_STOPPED_DAEMON
If a specific service is not running, use the following command:
As root user
/usr/local/afs7/bin/antidot start
Commands of the same type can be concatenated.
Example:
systemctl stop bo-ac.service
systemctl stop bo-analytics.service
systemctl stop bo-server.service
These three commands can be replaced by the following one:
systemctl stop bo_ac.service bo_analytics.service bo_server.service