Red Hat Bugzilla – Bug 837731
Script Server not working for mongoDB
Last modified: 2013-07-01 13:40:49 EDT
Description of problem:
We’ve setup three nodes with RHEL5.3 and same hardware specifications. One node installed with RHQ server and remaining two each installed with mongoDB and RHQ agent to monitor mongoDB.
I’ve discovered that RHQ 4.4 Script Server plugin is not working for mongoDB version 2.0.3. The initial availability scan indicates mongoDB is UP but thereafter it unable to detect the availability change (Goes Down and Goes UP). After the initial scan It is always showing UP.
Version-Release number of selected component (if applicable):
Create a new script server to monitor mongoDB. After the initial availability scan it unable to detect the availability change thereafter.
Steps to Reproduce:
1. Create a new script server
2. Executable value is /etc/init.d/mongod
3. Availability Execute Check set to YES
4. Availability Output Regex value is .*running.*
5. Availability Arguments value is status
Unable to detect availability change (Goes Up and Goes Down).
Should be able to update availability change very quickly.
could you please append the output when runnign /etc/init.d/mongod
- the server is running
- the server is not running
Could it be that the script needs a 'status' keyword appended as many services
I don't have a test instance handy to directly check it.
I also wonder if some more simple script that shows above behavior could be
created so that we can add that as a test case to the plugin.
This may be related to Bug 848258
I think this is probably related to bug #848258 as heiko mentioned. That bug has been addressed, so this issue might be fixed already with that one.