[root@hostname db]# systemctl restart postgresql-9.4 Failed to restart postgresql-9.4.service: Unit is not loaded properly: Invalid argument. See system logs and 'systemctl status postgresql-9.4.service' for details.
Please note: Depending upon the installation type (Privileged or Unprivileged) - Paths and Users required to perform the following steps, will vary. Please use caution in performing these steps, and verify the correct user runs the commands.
For Privileged installs, you may find the user as either "root" or a username in relation to the service running (ie: postgres, pgbouncer, phantom, etc). For Unprivileged installs you will likely see "phantom" or another specifically named account used during installation of SOAR.
Performing systemctl status postgresql-9.4.service:
[root@hostname db]# systemctl status postgresql-9.4.service ● postgresql-9.4.service Loaded: error (Reason: Invalid argument) Active: inactive (dead) Aug 01 10:27:21 fqdn systemd[1]: postgresql-9.4.service lacks both ExecStart= and ExecStop= setting. Refusing. Aug 01 10:27:21 fqdn systemd[1]: Cannot add dependency job for unit postgresql-9.4.service, ignoring: Unit is not loaded...gument. Aug 01 10:27:51 fqdn systemd[1]: postgresql-9.4.service lacks both ExecStart= and ExecStop= setting. Refusing. Aug 01 10:27:51 fqdn systemd[1]: postgresql-9.4.service lacks both ExecStart= and ExecStop= setting. Refusing. Aug 01 10:27:52 fqdn systemd[1]: postgresql-9.4.service lacks both ExecStart= and ExecStop= setting. Refusing. Aug 01 10:27:53 fqdn systemd[1]: postgresql-9.4.service lacks both ExecStart= and ExecStop= setting. Refusing. Aug 01 10:27:53 fqdn systemd[1]: postgresql-9.4.service lacks both ExecStart= and ExecStop= setting. Refusing. Aug 01 10:27:58 fqdn systemd[1]: postgresql-9.4.service lacks both ExecStart= and ExecStop= setting. Refusing. Hint: Some lines were ellipsized, use -l to show in full.
[root@hostname db]# /<phantom_home>/bin/start_phantom.sh Starting all Phantom services psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.6432"? psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.6432"? psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.6432"? psql: could not connect to server: No such file or directory
Please note: Depending upon the installation type (Privileged or Unprivileged) - Paths and Users required to perform the following steps, will vary. Please use caution in performing these steps, and verify the correct user runs the commands.
For Privileged installs, you may find the user as either "root" or a username in relation to the service running (ie: postgres, pgbouncer, phantom, etc). For Unprivileged installs you will likely see "phantom" or another specifically named account used during installation of SOAR.
Performing the Workaround by doing the following:
a. To startup the Postgres service
sudo -su postgres /usr/pgsql-9.4/bin/pg_ctl start -D /opt/phantom/data/db/ -s -w -t 300
sudo -su postgres /usr/bin/pgbouncer -d -q /etc/pgbouncer/pgbouncer.ini
/<phantom_home>/bin/start_phantom.sh
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
28-Sep-2026
|
Initial Release |