-
Notifications
You must be signed in to change notification settings - Fork 10
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
More troubleshooting documentation #8
Comments
postgres@opm=# SELECT grant_dispatcher('wh_nagios', 'user1'); this is which user? |
db_user=YOUR_USER |
They're both referring to the same postgres role which import data in the warehouse. I'll add some comments to make it clearer, thanks for the report! |
@rjuju Hi, when use morbo or hypnotoad but something wrong with it. should need other config or package? Thanks! Arctic66:/usr/local/src/opm2.4/opm-core-REL_2_4/ui # /usr/local/perl/bin/morbo script/opm Arctic66:/usr/local/src/opm2.4/opm-core-REL_2_4/ui # /usr/local/perl/bin/hypnotoad -f script/opm |
Apparently, with morbo you need to specify a path (for instance ./script/opm are advised). According to logs from hypnotoad, you're missing DBI, and probably DBD::Pg perl modules. Please refer to http://opm.readthedocs.io/opm-core/Installation.html#user-interface for the UI requirements. |
@rjuju Thank you very much! After install DBI and DBD::Pg, the problem was solved! How the check_pgactivity work in the monitor project. Can you share some solution for me? |
Sorry for late replky @wenJanus. I'm not sure I get your question. check_pgactivity is a probe for nagios dedicated for postgres. You must have a working nagios (or any fork available) to perform the needed checks on your servers. Once the checks are performed and perfdata are generated, you should see the UI getting updated automatically, provided you configured all the other steps documented (configuring nagios for perfdata output, setting up nagios_dispatcher and calling the wh_nagios.dispatch_record() function). |
Add the tips provided by @tabdoelhafiezkhan in OPMDG/opm-core#36
The text was updated successfully, but these errors were encountered: