Can't open PID file when starting PMDB_Platform_Vertica.service

Document ID:KM03640804
Creation Date:20-May-2020
Modified Date:20-May-2020
- Micro Focus Products:
  operations bridge reporter 10.40

Summary

When trying to start Vertica service is not able to find PID file

Error

Job for HPE_PMDB_Platform_Vertica.service failed because a configured resource limit was exceeded. See "systemctl status HPE_PMDB_Platform_Vertica.service" and "journalctl -xe" for details.

# systemctl status HPE_PMDB_Platform_Vertica.service

systemd[1]: New main PID 22713 does not belong to service, and PID file is not owned by root...using.

systemd[1]: Can't open PID file /opt/HP/database/catalog/pmdb/v_pmdb_node0001_catalog/vertica.p...rectory

systemd[1]: PID file /PMDB/v_PMDB_node0001_catalog/vertica.pid not readable (yet?) after start.

Cause

Cannot find PID file location correctly in file /usr/lib/systemd/system/HPE_PMDB_Platform_Vertica.service

Fix

Check that file has the PIDFile location is correct if not then find the vertica.pid location normally in catalog folder location on node folder v_pmdb_node0001 and correct the PIDFile variable with the correct location:

1) Check file location

# cat /usr/lib/systemd/system/HPE_PMDB_Platform_Vertica.service

[Unit]

Description=HPE Operation Bridge Reporter Vertica

After=network.target

[Service]

Type=forking

PIDFile=/opt/catalog/pmdb/v_pmdb_node0001_catalog/vertica.pid

ExecStart=/opt/HP/BSM/PMDB/bin/HPE_PMDB_Platform_Vertica start

ExecStop=/opt/HP/BSM/PMDB/bin/HPE_PMDB_Platform_Vertica stop

ExecReload=/opt/HP/BSM/PMDB/bin/HPE_PMDB_Platform_Vertica restart

# RemainAfterExit=yes

TimeoutStartSec=0

TimeoutStopSec=0

KillMode=none

2) Edit the file /usr/lib/systemd/system/HPE_PMDB_Platform_Vertica.service and change to the correct PIDFile location

3) Reload the daemon change done:

#systemctl daemon-reload