search cancel

Vertica DB Daemon shows as 'inactive (dead)'

book

Article ID: 258171

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

When I check the verticad status is show as in the example below:

# systemctl status verticad
● verticad.service - Vertica server restart oneshot
   Loaded: loaded (/etc/systemd/system/verticad.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Tue 2022-12-27 14:08:51 UTC; 3 weeks 2 days ago
  Process: 520 ExecStart=/opt/vertica/sbin/verticad start (code=exited, status=0/SUCCESS)
 Main PID: 520 (code=exited, status=0/SUCCESS)

Dec 27 14:08:46 my_dr systemd[1]: Starting Vertica server restart oneshot...
Dec 27 14:08:48 my_dr su[647]: (to dradmin) root on none
Dec 27 14:08:51 my_dr verticad[520]: Vertica: start OK for users: dradmin
Dec 27 14:08:51 my_dr verticad[520]: [  OK  ]
Dec 27 14:08:51 my_dr systemd[1]: Started Vertica server restart oneshot.

Environment

Release : 22.2

Cause

This is a oneshot service type which we see in the output as well (green marker).

It is expected to see this service as inactive (dead) after initial execution.

Resolution

Working as expected.

Additional Information

https://www.redhat.com/sysadmin/systemd-oneshot-service