tomcat rc.local lxc
by lambo69 from LinuxQuestions.org on (#51XWY)
Hello,
i'm running different Slackware-installs inside lxc-containers on a Slackware-host. Each container runs tomcat; tomcat should be started from /etc/rc.d/rc.local.
The problem: there's only one container where tomcat really is started. On the other containers, tomcat doesn't come up on startup, if called from rc.local.
It's possible to start it from a shell, i tried different approaches: using /etc/rc.d/rc.tomcat, using $CATALINA_HOME/bin/startup.sh or $CATALINA_HOME/bin/catalina.sh, always with the same result: it run's from shell, but not from rc.local. I traced the call from rc.local on startup into the suitable section of catalina.sh, everything seems to be fine, but tomcat doesn't start.
I increased log-level of tomcat and emptied catalina.out before restart: when running from rc.local at startup, catalina.out remains empty. Even running rc.local from a shell works fine. Other commands in rc.local are executed at startup, just starting tomcat fails (no matter if started as a background-process [happens anyway in catalina.sh], or not, or at which position in rc.local it is called).
I copied startup-scripts from the working container to those, which fail, took care on owners/permissions, nothing helped, i compared file-permissions on the host-system, everything looks identical.
Has anyone an idea on how to fix this strange behaviour, or on how to find out, what happens?
thanks in advance
lambo
i'm running different Slackware-installs inside lxc-containers on a Slackware-host. Each container runs tomcat; tomcat should be started from /etc/rc.d/rc.local.
The problem: there's only one container where tomcat really is started. On the other containers, tomcat doesn't come up on startup, if called from rc.local.
It's possible to start it from a shell, i tried different approaches: using /etc/rc.d/rc.tomcat, using $CATALINA_HOME/bin/startup.sh or $CATALINA_HOME/bin/catalina.sh, always with the same result: it run's from shell, but not from rc.local. I traced the call from rc.local on startup into the suitable section of catalina.sh, everything seems to be fine, but tomcat doesn't start.
I increased log-level of tomcat and emptied catalina.out before restart: when running from rc.local at startup, catalina.out remains empty. Even running rc.local from a shell works fine. Other commands in rc.local are executed at startup, just starting tomcat fails (no matter if started as a background-process [happens anyway in catalina.sh], or not, or at which position in rc.local it is called).
I copied startup-scripts from the working container to those, which fail, took care on owners/permissions, nothing helped, i compared file-permissions on the host-system, everything looks identical.
Has anyone an idea on how to fix this strange behaviour, or on how to find out, what happens?
thanks in advance
lambo