iManager/Tomcat does not automatically start after SLES11 (SysV) upgrade to SLES12(systemd)

  • 7023866
  • 09-May-2019
  • 25-Jun-2019

Environment

SUSE Linux Enterprise Server 12 Service Pack 4 (SLES 12 SP4)

iManager 3.1.1

Situation

iManager 3.1.1 was installed while the OS was still SLES 11 SP4 (SysV).  
OS was then upgraded to SLES12 SP4 (systemd) and tomcat/iManager no longer auto-started at boot time.


Resolution

Execute the following commands to create entries into systemd and cause Tomcat8 to automatically start after a server reboot.

cp -f /etc/opt/novell/tomcat8/init.d/tomcat8-service.service /usr/lib/systemd/system/novell-tomcat8-service.service

chown -R novlwww:novlwww /usr/lib/systemd/system/novell-tomcat8-service.service

/usr/bin/systemctl enable /usr/lib/systemd/system/novell-tomcat8-service.service

systemctl start novell-tomcat8-service.service

 


Cause

When iManager 3.1 was installed the OS was SLES11 (SysV) and it used /usr/sbin/rcnovell-tomcat8 to start/stop iManager.

Upgrading to SLES12 removed that symbolic link but did not enable the /etc/opt/novell/tomcat8/init.d/tomcat8-service.service in systemd

Feedback service temporarily unavailable. For content questions or problems, please contact Support.