Please note that the Forum is a place where people engage voluntarily and on the topics they could relate to or with which they could help. Bumping up the same post several times with no additional data, for example, that appeared in the course of your own research of the issue, are usually not helpful, and creates uninformative messages.
Please try to look into other posts on the related issues in the forum – they might have helpful information and hopefully provide additional details to this case. It is possible that the results of your additional research could help Community Members help you.
The problem is : Status: instance CHECK_MK_POSTGRES is not running or postgres DATADIR name is not identical with instance nameCRIT, Version: PostgreSQL 14.10 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22.0.1), 64-bit
I can’t understand why the script said [INSTANCE] naming while there is no concept of [INSTANCE_NAME] in PostgreSQL like Oracle or SQL Server.
for line in postgres_cfg:
if line.startswith("#") or "=" not in line:
continue
line = line.strip()
key, value = line.split("=")
if key == "DBUSER":
dbuser = value.rstrip()
if key == "PG_BINARY_PATH":
pg_binary_path = value.rstrip()
if key == "INSTANCE":
env_file, pg_user, pg_passfile, instance_name = _parse_INSTANCE_value(
value, config_separator
)
pg_database, pg_port, pg_version = parse_env_file(env_file)
When the python script read postgres.cfg, it searches 4 arguments, in the documentation i always found 3 :
Env File
User
PGPASS
It’s possible to add a fourth argument to customize “INSTANCE_NAME”.’
Environment File for Checkmk
OLD NAME : /etc/check_mk/main.env
NEW NAME : /etc/check_mk/dbpgtst.env
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.