Open anamehra opened 1 year ago
@abdosi , FYI.
This may be expected because the monit may start later, to allow for the system init to complete. Can you check the same on a pizzabox and see if there is difference?
On pizzabox as well I see that its takes ~5 mins after monit process up to recognize disk issue. If this is expected behavior, we can close this issue.
During a sonic-mgmt run on Chassis LC, our pre-sanity script reported 'monit status' check failure due to low disk soace. The recovery action was to reboot the card. Reboot may not be able to recover the system in such scenatio most of the time. Is it right thing to do?
After reboot, the pre-sanity check pass on 'monit status' though the disk usage was still high. After some debugging, I found that it took monit process ~14 mins to report disk issue. Is this expected behavior? May this be improved?
Description
Steps to reproduce the issue:
1. 2. 3.
Describe the results you received:
Describe the results you expected:
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):