Trouble creating new rcXXXX service
Sorry to repost - I changed subject so its not perceived as a Java/Tomcat issue. I thought this would be common SuSE issue. I have read the /etc/init.d/skeleton files and do not find any reference to a registry of services (other than /etc/init.d/*). My problem is trying to clone existing script /etc/init.d/tomcat to a new one (/etc/init.d/tomcat55) that runs a new version of the Tomcat application server. NOTE: We are running SLES9 on AMD64, but I assume the rc script framework/conventions are the same on SuSE Pro 9.2 and SLES9 (that's why I am posting on both lists). Apologies if this is not correct. Anyway, I have SLES9 servers running the Jakarta Tomcat 5.0.19 application server that comes with SLES9. Due to some clustering/failover problems I need to upgrade to the latest Tomcat 5.5.7 and apply some provided patches. Here's what I did: 1. Expanded the ".gz" file in the home directory of the user that the app server will run under. 2. Copied the /etc/init.d/tomcat script to /etc/init.d/tomcat55 and changed the appropriate references to "tomcat" to "tomcat55". 3. Made corresponding adjustements to /etc/sysconfig/j2ee (actually a copy called tomcat55 and referenced it from the init.d script). 4. I can now start and stop using "/etc/init.d/tomcat55 start" and /etc/init.d/tomcat55 stop" with no problem. 5. However when I go to install the script it fails with these messages: kingfish:/etc/init.d # insserv /etc/init.d/tomcat55 insserv: script tomcat.20050216a: service tomcat already provided! insserv: script tomcat: service tomcat already provided! kingfish:/etc/init.d # Here is the header for my /etc/init.d/tomcat55 script: # # /etc/init.d/tomcat55 # # and symbolic its link # # /usr/sbin/rctomcat55 # # System startup script for the Tomcat servlet container # ### BEGIN INIT INFO # Provides: tomcat55 # Required-Start: $local_fs $remote_fs # X-UnitedLinux-Should-Start: $named $syslog $time # Required-Stop: $local_fs $remote_fs # X-UnitedLinux-Should-Stop: $named $syslog $time # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Short-Description: Tomcat Servlet Container - Version 5.5.x # Description: Start Tomcat 5.5.x to allow JAVA server pages ### END INIT INFO What am I missing? Thank you in advance - Richard
Richard Mixon (qwest) wrote:
Sorry to repost - I changed subject so its not perceived as a Java/Tomcat issue. I thought this would be common SuSE issue. I have read the /etc/init.d/skeleton files and do not find any reference to a registry of services (other than /etc/init.d/*).
My problem is trying to clone existing script /etc/init.d/tomcat to a new one (/etc/init.d/tomcat55) that runs a new version of the Tomcat application server.
<SNIP>
5. However when I go to install the script it fails with these messages: kingfish:/etc/init.d # insserv /etc/init.d/tomcat55 insserv: script tomcat.20050216a: service tomcat already provided! insserv: script tomcat: service tomcat already provided! kingfish:/etc/init.d #
Never mind. I moved the backup (tomcat.20050216a) and it stopped complaining. It did create the runlevel links: kingfish:/etc/init.d # insserv -v /etc/init.d/tc55 enable service ../tc55 -> /etc/init.d/rc3.d/S16tc55 enable service ../tc55 -> /etc/init.d/rc3.d/K06tc55 enable service ../tc55 -> /etc/init.d/rc5.d/S16tc55 enable service ../tc55 -> /etc/init.d/rc5.d/K06tc55 However it does not create the link /usr/sbin/rctc55 that I would expect. No matter - I manually created it, but it seems strange to either not have created it or at least complained somehow. - Richard
However it does not create the link /usr/sbin/rctc55 that I would expect. No matter - I manually created it, but it seems strange to either not have created it or at least complained somehow. I think there is a misunderstanding. insserv only manages the start stop links, not the rc links in /usr/sbin. Those links are actually a
Richard Mixon (qwest) wrote: part of the rpm. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe Morris (NTM) wrote:
However it does not create the link /usr/sbin/rctc55 that I would expect. No matter - I manually created it, but it seems strange to either not have created it or at least complained somehow. I think there is a misunderstanding. insserv only manages the start stop links, not the rc links in /usr/sbin. Those links are actually a
Richard Mixon (qwest) wrote: part of the rpm.
Joe, thanks for clearing that up. Yes, a big misunderstanding on my part. -Richard
"Richard Mixon (qwest)" <rnmixon@qwest.net> [18 Feb 2005 13:24 -0700]:
However it does not create the link /usr/sbin/rctc55 that I would expect.
Why should it? There's nothing on a SUSE system that does create such links and there never was. These /usr/sbin/rcXXX symlinks are part of the rpm package that provides the given service.
No matter - I manually created it, but it seems strange to either not have created it or at least complained somehow.
Why should it complain? these rcXXX symlinks are just a convenience for users, the system itself neither needs nor uses them. Philipp
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Mixon (qwest) wrote: <snip>
What am I missing?
OK, I'll bite. What you've done doesn't seem unreasonable to me at first glance. But maybe there isn't enough differentiation between "tomcat" and "tomcat55" -- could it be discounting any numerical versioning info on purpose? What happens is you change it to "thomcat55" :-) - - Carl - -- ____________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Key #0x68396713 Reg. Linux User #350527 http://counter.li.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCFlAOusxgymg5ZxMRAm86AJ9Tcped/aUNAOrq6OF0rjP1bdNCSgCffZpf 0jSsmB/mhGOCccfLiGjo8PQ= =c4Vx -----END PGP SIGNATURE-----
Carl E. Hartung wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Richard Mixon (qwest) wrote: <snip>
What am I missing?
OK, I'll bite. What you've done doesn't seem unreasonable to me at first glance. But maybe there isn't enough differentiation between "tomcat" and "tomcat55" -- could it be discounting any numerical versioning info on purpose?
What happens is you change it to "thomcat55" :-)
Carl, Thanks for the "bite". I just replied to my own post with most of the solution. However changing it from tomcat to tc55 did not work cleanly either. innserv did create the runlevel links correctly but would not create the rcxxx link in /usr/sbin, but did not complain either. Go figure. As I posted, creating the link manually was easy enough. Thanks - Richard
participants (4)
-
Carl E. Hartung -
Joe Morris (NTM) -
Philipp Thomas -
Richard Mixon (qwest)