Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template triggers Disaster Alert frequently for "All FMS Processes" because PS state returns U #11

Open
kriggleman42 opened this issue Apr 1, 2022 · 0 comments

Comments

@kriggleman42
Copy link

kriggleman42 commented Apr 1, 2022

We are using Zabbix 6 to monitor our FileMaker 19 server which is now running on MacOS Monterey 12.2 release.
I'm updating my Soliant template because the output of PS command returns a state of U fairly frequently.
Therefore, the current template triggers the Disaster Alert on a regular basis and then resolves itself in the next check or so.

Here are PS states I found from https://gist.github.com/jhyland87/6ff0266abc9a9b57690ab28dfc18c180 which is 5 years old so I'm not sure why we didn't see before. Perhaps we see now because we are running on new Apple M1 architecture, I'm not sure. It could also be that new Zabbix 6 Reports - "Triggers Top 100" makes it much more obvious how often trigger is being fired.

Here is doc on State from above link:
state The state is given by a sequence of characters, for example, ``RWNA''. The first character indicates the run state of the process:

       I       Marks a process that is idle (sleeping for longer than
	       about 20 seconds).
       R       Marks a runnable process.
       S       Marks a process that is sleeping for less than about 20
	       seconds.
       T       Marks a stopped process.
       **U       Marks a process in uninterruptible wait.**
       Z       Marks a dead process (a ``zombie'').

The disaster alert is being triggered whenever the process state is "U". I resolved on my own but wanted to report for benefit of others. It's a simple matter of adding a U to the preprocessing check on multiple triggers using "All FMS Processes" item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant