opmdg/opm-doc

Global documentation of the project

opm-doc's Issues

Nginx as websever

Example nginx config for forwarding request to a hypnotoad application server:

upstream hypnotoad {
  server 127.0.0.1:8080;
}

server {
  listen 80;

  location / {
        proxy_pass http://hypnotoad;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto "http";
  }
}

You should ensure that hypnotoad starts on boot, e.g. in /etc/rc.local

su - www-data -c 'hypnotoad /var/www/opm-core/ui/script/opm'

Function calls for installation do not work

The documentation says to make the following calls as part of the installation, but both fail. The functions exist, but the parameters seem to be wrong.

SELECT create_user('admin1', 'admin1'); opm=# SELECT create_user('admin1', 'admin1'); ERROR: function create_user(unknown, unknown) does not exist LINE 1: SELECT create_user('admin1', 'admin1'); ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts.

SELECT wh_nagios.dispatch_record(true)

opm=# SELECT create_user('admin1', 'admin1'); ERROR: function create_user(unknown, unknown) does not exist LINE 1: SELECT create_user('admin1', 'admin1'); ^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
opm=# SELECT wh_nagios.dispatch_record(true); ERROR: function wh_nagios.dispatch_record(boolean) does not exist LINE 1: SELECT wh_nagios.dispatch_record(true); ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts.

Not able to start with morbo OPM application

Hi,
In this part of doc:

user:/usr/local/src/opm/opm-core/ui/opm$ morbo script/opm
[Fri Nov 29 12:12:52 2013] [debug] Helper "url_for" already exists, replacing.
[Fri Nov 29 12:12:52 2013] [debug] Reading config file "/home/ioguix/git/opm/ui/opm/opm.conf".
[Fri Nov 29 12:12:53 2013] [info] Listening at "http://*:3000".
Server available at http://127.0.0.1:3000.

should be

root:/usr/local/src/opm/opm-core/ui# morbo ./script/opm
[Tue Apr 24 15:35:41 2018] [debug] Reading configuration file "/usr/local/src/opm/opm-core/ui/opm.conf".
[Tue Apr 24 15:35:41 2018] [debug] Helper "url_for" already exists, replacing.
[Tue Apr 24 15:35:41 2018] [info] Listening at "http://*:3000".
Server available at http://127.0.0.1:3000.

The ./ before

script/opm

is mandatory
@PaulemDevadder

Please answer "why?" early in the docs.

I looked at this: https://opm.readthedocs.io/

Unfortunately like most software docs, your docs start with details.

Please answer the question "why?" early in the docs.

Why is OPM great? Benefits, why better then powa, PGObserver, ....?

More troubleshooting documentation

Add the tips provided by @tabdoelhafiezkhan in OPMDG/opm-core#36

check_postgres support

Hello,

Does OPM support output of check_postgres https://bucardo.org/wiki/Check_postgres ?

Icinga2 config

OPM could be used with Icinga2, you have to enable perfdata feature:

 $ icinga2 feature enable perfdata

configure data format in /etc/icinga2/features-enabled/perfdata.conf:

library "perfdata"

object PerfdataWriter "perfdata" {

  host_perfdata_path = "/var/spool/icinga2/perfdata/host-perfdata"

  service_perfdata_path = "/var/spool/icinga2/perfdata/service-perfdata"

  rotation_interval = 15s

  host_format_template = "DATATYPE::HOSTPERFDATA\tTIMET::$icinga.timet$\tHOSTNAME::$host.name$\tHOSTPERFDATA::$host.perfdata$\tHOSTCHECKCOMMAND::$host.check_command$\tHOSTSTATE::$host.state$\tHOSTSTATETYPE::$host.state_type$\tHOSTOUTPUT::$host.output$"
  service_format_template = "DATATYPE::SERVICEPERFDATA\tTIMET::$icinga.timet$\tHOSTNAME::$host.name$\tSERVICEDESC::$service.name$\tSERVICEPERFDATA::$service.perfdata$\tSERVICECHECKCOMMAND::$service.check_command$\tHOSTSTATE::$host.state$\tHOSTSTATETYPE::$host.state_type$\tSERVICESTATE::$service.state$\tSERVICESTATETYPE::$service.state_type$\tSERVICEOUTPUT::$service.output$"
}

Icinga2 has different macros names than Nagios, for complete list see documentation.

Hypnotoad won't start because of method 'bridge' not found

Don't know if this is a documentation issue though. I followed the documentation, but when starting "hypnotoad /usr/local/src/opm/opm-core-master/ui/script/opm", I get the following error:

Can't load application from file "/usr/local/src/opm/opm-core-master/ui/script/opm": Can't locate object method "bridge" via package "Mojolicious::Routes" at /usr/local/src/opm/opm-core-master/ui/script/../lib/OPM.pm line 103.

OPM client issue

Hi Team,

I have installed OPM and but unable to see any clients.Could you please let me know what has to be done in destination server.

Restoring & pg_restore -j

Both extensions (omp-core & wh_nagios) create their tables during the CREATE EXTENSION, including foreign keys. So we had a pg_restore -j8 --section=data of an OPM database that failed, because it was parallelized, the extensions tables data were not loaded sequentially, and the foreign keys were already there.

The doc should state an official upgrade procedure, eg:

• separate pg_restore for extension tables (not parallelized) and other ones (parallelized), with pg_restore -l and -L
• pg_restore --disable-triggers 😱
• an official script to drop and recreate manually the constraints
• something else that I didn't think of.

pg_upgrade fails

pg_upgrade of an OPM database fails with the following error message. The api table is part of opm-core. Documenting a turnaround would be fine (I didn't try).

Your installation contains one of the reg* data types in user tables.
These data types reference system OIDs that are not preserved by
pg_upgrade, so this cluster cannot currently be upgraded.  You can
remove the problem tables and restart the upgrade.  A list of the problem
columns is in the file:
    tables_using_reg.txt

cat tables_using_reg.txt 
Database: opm
  public.api.proc
  public.api_pkey.proc