The syncconf.sh monitoring command might report incorrect monitoring status after successfully completing the operation.
If all of the monitoring agents are running before you run the syncconf.sh monitoring command, the command might report the monitoring status as "stopped" after the configuration synchronization operation is finished.
If you run the status.sh monitoring command, the results should show that all of the monitoring agents are running.
Resolving the problem
After you run the syncconf.sh monitoring command, check the monitoring status by running the syncconf.sh monitoring command on the InfoSphere BigInsights Console node as the BigInsights Administrator user.