After the Network flow analysis Harvester server reboot, systemctl status nfa_mysqlCSE shows failed
systemctl status nfa_mysqlCSE
● nfa_mysqlCSE.service
Loaded: loaded (/etc/rc.d/init.d/nfa_mysqlCSE; generated)
Active: failed (Result: exit-code) since Fri 2024-04-12 12:00:55 UTC; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 815 ExecStart=/etc/rc.d/init.d/nfa_mysqlCSE start (code=exited, status=3)
Tasks: 36 (limit: 203744)
Memory: 473.1M
CGroup: /system.slice/nfa_mysqlCSE.service
└─899 /opt/CA/NFA/Netflow/bin/mysqld --defaults-file=/opt/CA/NFA/Netflow/my.cnf --basedir=/opt/CA/NFA/Netflow --datadir=/opt/CA/NFA/Netflow/data --user=nfa --log-error=/opt/CA/NFA/Netflow/data/localhost.localdomain.err --pid-file=/opt/CA/N>
Apr 12 12:00:24 localhost.localdomain systemd[1]: Starting nfa_mysqlCSE.service...
Apr 12 12:00:55 xxxxx-harvester-linux8 nfa_mysqlCSE[852]: [55B blob data]
Apr 12 12:00:55 xxxxx-harvester-linux8 systemd[1]: nfa_mysqlCSE.service: Control process exited, code=exited status=3
Apr 12 12:00:55 xxxxx-harvester-linux8 systemd[1]: nfa_mysqlCSE.service: Failed with result 'exit-code'.
Apr 12 12:00:55 xxxxx-harvester-linux8 systemd[1]: Failed to start nfa_mysqlCSE.service
however
service nfa_mysqlCSE status
MySQL CSE running (899) [ OK ]
DX NetOps Network flow analysis - All releases
Expected Behavior
Engineering clarified that this inconsistency is an expected behavior following a system reboot, as the "systemctl" command is not supported for checking service status. Instead, the recommended approach is to utilize the commands "/etc/init.d/nfa_* status" and "service nfa_mysqlCSE status" for accurate service status verification.
Solution: