Did this article resolve your question/issue?



How to autostart AdminService on Linux with systemctl scripts?


TitleHow to autostart AdminService on Linux with systemctl scripts?
URL NameHow-to-autostart-AdminService-on-Linux-with-systemctl-scripts
Article Number000178822
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: Linux
Other: AdminServer, systemctl
Question/Problem Description
​How to auto-start the AdminServer on Linux with a systemctl service file script?
How to ensure the AdminServer remains running on Linux when the root user logs out?
How to start the AdminServer on a Linux Server in a similar to the AdminService on Windows?
What systemctl service commands need to be configured so that the AdminServer autostarts on Linux ?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Example systemctl service file to start the AdminService.  The following is provided 'as-is'. Any issues will need to be further explored with a Linux Administrator. 

1)  cd  /etc/systemd/system

2)  sudo su

3)  vi admsrvc.service

Change the values in the file sample below for ExecStart and ExecStop to point to the correct installation directory.

Sample systemctl service file

Description=AdminService for OpenEdge

ExecStart=/usr/dlc/bin/proadsv -start
ExecStop=/usr/dlc/bin/proadsv -stop


4)  To start / stop the AdminServer :
$   sudo systemctl daemon-reload​
$   sudo systemctl start admsrvc
$   sudo systemctl stop admsrvc

Once the AdminService is started with the "systemctl start admsrvc" command, all databases and ubrokers configured to autostart will be started by the AdminServer.

5) To enable the service to start at boot time:

sudo systemctl enable admsrvc

Note: Although the steps above refers to the AdminServer, the same methodology can be applied in order to start PASOE instances and fathom ( See example in 000096181, Openedge 12 fathom won't start
Last Modified Date11/19/2019 7:37 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.