You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
monit tool is logging error logs in syslog as "sflowd is not running", which is causing the log analyzer from ptf to fail
Steps to reproduce the issue:
config reload or reboot
Describe the results you received:
Error logs
sonic ERR monit[377]: 'sflowmgrd' process is not running
root@sonic:/home/admin# systemctl status sflow
● sflow.service
Loaded: masked (Reason: Unit sflow.service is masked.)
Active: inactive (dead) since Fri 2019-02-15 05:26:42 UTC; 10min ago
Main PID: 14583 (code=exited, status=0/SUCCESS)
Describe the results you expected:
No errors to be logged
This can be fixed by enabling sflow service in init_cfg.json.j2.
But need to know what is the reason for disabling sflow? was it causing delayed startup or any ?
Why the monit script is checking for a disabled service?
Why the monit script is checking for a disabled service?
The Monit to monitor the processes in sflow container is merged into repo before sflow service is disabled. Right now I am working on the solution which will not monitor the processes in the service according to whether such service is enabled or disabled in configuration file.
Description
monit tool is logging error logs in syslog as "sflowd is not running", which is causing the log analyzer from ptf to fail
Steps to reproduce the issue:
Describe the results you received:
Error logs
sonic ERR monit[377]: 'sflowmgrd' process is not running
root@sonic:/home/admin# systemctl status sflow
● sflow.service
Loaded: masked (Reason: Unit sflow.service is masked.)
Active: inactive (dead) since Fri 2019-02-15 05:26:42 UTC; 10min ago
Main PID: 14583 (code=exited, status=0/SUCCESS)
Describe the results you expected:
No errors to be logged
Additional information you deem important (e.g. issue happens only occasionally):
This relates to
#4137
sonic-net/sonic-utilities#944
The text was updated successfully, but these errors were encountered: