Did this article resolve your question/issue?



AdminServer is not auto starting on remote container

« Go Back


TitleAdminServer is not auto starting on remote container
URL Nameadminserver-is-not-auto-starting-on-remote-container
Article Number000114432
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
AdminServer is not auto starting on remote container.
One remote container auto starts the AdminServer after the server restarts, while the other container does not. 
Steps to Reproduce
Clarifying Information
Checked crontab and there was no jobs for the AdminServer there. 
Checked the steps outlined under article 000074464 and the Adminserver is not configured with systemctl.

Error Message
Defect/Enhancement Number
Checked the rc directories under init.d and the machine that auto starts has a symbolic link to a script that starts the AdminServer while the other does not. 
The AdminServer in question needs to be configured to autostart.
The configuration varies per OS.

000074464, How to autostart AdminService on Linux with systemctl scripts?

Last Modified Date9/12/2018 6:09 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.