https://communities.sas.com/t5/Administration-and-Deployment/Error-when-starting-SAS-Viya-services/m-p/863626#M26202 [unxsas@srvsaspsqlpr ~]$ sudo systemctl start sas-viya-consul-default<BR />[unxsas@srvsaspsqlpr ~]$ sudo systemctl start sas-viya-sasdatasvrc-postgres-node0 &amp;&amp; sudo systemctl start sas-viya-sasdatasvrc-postgres-pgpool0<BR />Job for sas-viya-sasdatasvrc-postgres-node0.service failed because a timeout was exceeded. See "systemctl status sas-viya-sasdatasvrc-postgres-node0.service" and "journalctl -xe" for details.<BR />[unxsas@srvsaspsqlpr ~]$ systemctl status sas-viya-sasdatasvrc-postgres-node0.service<BR />● sas-viya-sasdatasvrc-postgres-node0.service - LSB: start and stop postgresql service for postgres cluster<BR />Loaded: loaded (/etc/rc.d/init.d/sas-viya-sasdatasvrc-postgres-node0; bad; vendor preset: disabled)<BR />Active: failed (Result: timeout) since Sun 2023-03-12 00:33:58 +01; 1min 10s ago<BR />Docs: man:systemd-sysv-generator(8)<BR />Process: 13534 ExecStart=/etc/rc.d/init.d/sas-viya-sasdatasvrc-postgres-node0 start (code=killed, signal=TERM)<BR />Tasks: 0<BR /><BR />Mar 12 00:28:58 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: SAS_HOSTNAME=srvsaspsqlpr.sahamassurance.si....0<BR />Mar 12 00:28:58 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are not accessible. W.....<BR />Mar 12 00:30:02 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:31:05 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:32:08 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:33:12 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: sas-viya-sasdatasvrc-postgres-node0.service start operation timed out. T...ting.<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: Failed to start LSB: start and stop postgresql service for postgres cluster.<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: Unit sas-viya-sasdatasvrc-postgres-node0.service entered failed state.<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: sas-viya-sasdatasvrc-postgres-node0.service failed. Sun, 12 Mar 2023 00:28:50 GMT Youssef_Ben 2023-03-12T00:28:50Z https://communities.sas.com/t5/Administration-and-Deployment/Error-when-starting-SAS-Viya-services/m-p/863626#M26202 [unxsas@srvsaspsqlpr ~]$ sudo systemctl start sas-viya-consul-default<BR />[unxsas@srvsaspsqlpr ~]$ sudo systemctl start sas-viya-sasdatasvrc-postgres-node0 &amp;&amp; sudo systemctl start sas-viya-sasdatasvrc-postgres-pgpool0<BR />Job for sas-viya-sasdatasvrc-postgres-node0.service failed because a timeout was exceeded. See "systemctl status sas-viya-sasdatasvrc-postgres-node0.service" and "journalctl -xe" for details.<BR />[unxsas@srvsaspsqlpr ~]$ systemctl status sas-viya-sasdatasvrc-postgres-node0.service<BR />● sas-viya-sasdatasvrc-postgres-node0.service - LSB: start and stop postgresql service for postgres cluster<BR />Loaded: loaded (/etc/rc.d/init.d/sas-viya-sasdatasvrc-postgres-node0; bad; vendor preset: disabled)<BR />Active: failed (Result: timeout) since Sun 2023-03-12 00:33:58 +01; 1min 10s ago<BR />Docs: man:systemd-sysv-generator(8)<BR />Process: 13534 ExecStart=/etc/rc.d/init.d/sas-viya-sasdatasvrc-postgres-node0 start (code=killed, signal=TERM)<BR />Tasks: 0<BR /><BR />Mar 12 00:28:58 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: SAS_HOSTNAME=srvsaspsqlpr.sahamassurance.si....0<BR />Mar 12 00:28:58 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are not accessible. W.....<BR />Mar 12 00:30:02 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:31:05 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:32:08 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:33:12 srvsaspsqlpr sas-viya-sasdatasvrc-postgres-node0[13534]: WARNING: Consul/Vault are still not accessi.....<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: sas-viya-sasdatasvrc-postgres-node0.service start operation timed out. T...ting.<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: Failed to start LSB: start and stop postgresql service for postgres cluster.<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: Unit sas-viya-sasdatasvrc-postgres-node0.service entered failed state.<BR />Mar 12 00:33:58 srvsaspsqlpr systemd[1]: sas-viya-sasdatasvrc-postgres-node0.service failed. Sun, 12 Mar 2023 00:28:50 GMT https://communities.sas.com/t5/Administration-and-Deployment/Error-when-starting-SAS-Viya-services/m-p/863626#M26202 Youssef_Ben 2023-03-12T00:28:50Z https://communities.sas.com/t5/Administration-and-Deployment/Error-when-starting-SAS-Viya-services/m-p/863787#M26203 Looks like Consul/Vault isn't starting, you may want to look at those logs (/opt/sas/viya/config/var/log/consul/default) Mon, 13 Mar 2023 13:46:08 GMT https://communities.sas.com/t5/Administration-and-Deployment/Error-when-starting-SAS-Viya-services/m-p/863787#M26203 gwootton 2023-03-13T13:46:08Z