Custom Systemd Service Stops Immediately after Starting (Doc ID 2331979.1)

Last updated on JUNE 30, 2022

Applies to:

Symptoms

Service started with custom systemd script stops straight after starting

For example - /etc/systemd

/system/oracle.service

[Unit]
Description=Oracle Application Server Startup
After=network.target

[Service]
User=oracle
Group=oinstall
Type=simple
WorkingDirectory=/oracle/bin
ExecStart=/oracle/bin/apsinit_start.sh
ExecStop=/oracle/bin/apsinit_stop.sh
Restart=on-failure
RestartSec=1

[Install]
WantedBy=multi-user.target

Corresponding logs:

>>/var/log/messages

server1 systemd[1]: Startingd Oracle Application Server Startup.
server1 systemd[1]: Starting Oracle Application Server Startup...
server1 apsinit_start.sh[41176]: Starting RDBMS: REPOS
server1 apsinit_start.sh[41176]: Starting Domain: RMIBSDomain
server1 apsinit_start.sh[41176]: Starting Component: ohs1 (RMIBSDomain)
server1 apsinit_start.sh[41176]: Starting Component: RepServerMibsNeu2 (RMIBSDomain)
server1 apsinit_stop.sh[43727]: Stopping Component: ohs1 (RMIBSDomain)
server1 apsinit_stop.sh[43727]: Stopping Component: RepServerMibsNeu2 (RMIBSDomain)
server1 apsinit_stop.sh[43727]: Stopping Domain: RMIBSDomain
server1 apsinit_stop.sh[43727]: Stopping RDBMS: REPOS

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.