Re: [Wrapper-user] Not starting service on Solaris

[Christian M. <chr...@ta...>]

Glenn,

I think svc tries to start your applications twice because of this:

ln -s /etc/init.d/myapp /etc/rc0.d/K20myapp
ln -s /etc/init.d/myapp /etc/rc1.d/K20myapp
ln -s /etc/init.d/myapp /etc/rc2.d/S20myapp
ln -s /etc/init.d/myapp /etc/rc3.d/S20myapp

(see
http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-solaris.html)

As you can see, there is a S20myapp in the rc2.d & rc3.d folder.

this means, when the systems changes to init level 2, it will try to 'S'tart
myapp at sequence 20.
and it will try to start myapp at init level 3.

At boot solaris starts at init 0 and will traverse all init levels until
init level 3.
So when getting into init level 3 the myapp application was already started
at init 2.

As you see in the logfile the script will notice that your app has already
been started and quit, so it's not harmful to your system to leave the file
there, but on the other side I think it would also be safe to remove
rc2.d/S20myapp if you want.

Cheers,
Christian

On Fri, May 14, 2010 at 12:29 AM, <gle...@ag...> wrote:

>
> Thanks Christian, that worked. My service is starting on system start now,
> but it looks like it is getting started twice for some reason?
> /var/svc/log/milestone-multi-user-server:default.log now contains:
> Executing legacy init script “/etc/rc3.d/S20myapp.sh”.
> Starting MyApp...
> MyApp is already running.
> Legacy init script “/etc/rc3.d/S20myapp.sh” exited with return code 1.
>
> Kind Regards,
> *
> Glenn Potter | **Agfa HealthCare*
> Strategic Site Research Engineer | HE/Radiology PACS Solutions
> M  +1 414 208 8997
> gle...@ag...
> Milwaukee, WI USA (Central Time: GMT-06:00)
>
> Agfa HealthCare Corporation, 100 Challenger Road, Ridgefield Park, NJ,
> 07660-2199, United States
> http://www.agfa.com/healthcare/
>  ------------------------------
> Click on link to read important disclaimer:
> http://www.agfa.com/healthcare/maildisclaimer
>
>
>  *Christian <chr...@ta...>*
>
> 05/13/2010 01:16 AM
>  Please respond to
> wra...@li...
>
>   To
> wra...@li...
> cc
>   Subject
> Re: [Wrapper-user] Not starting service on Solaris
>
>
>
>
>
> Glenn,
>
> We are sorry for the confusion.
>
> Due to the parsing routines/naming conventions of SVC, you can not use
> capital letters for a command launched at rc level.
>
> Please try renaming the rc*.d/*MyApp.sh files to rc*.d/*myapp.sh
>
> Hope this works out for you.
>
> Cheers,
> Christian
>
> On Wed, 2010-05-12 at 23:54 -0500, gle...@ag... wrote:
> >
> > Hello,
> >
> > I deployed my wrapped application to Solaris 10 and installed
> > following the instructions on:
> >
> http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-solaris.html
> >
> > I can start and stop as a console app and background process from the
> > command line in /etc/init.d.
> >
> > When I reboot the service is not started and I get this
> > in /var/svc/log/milestone-multi-user-server:default.log:
> >
> > Executing legacy init script “/etc/rc3.d/S20MyApp.sh”.
> > Usage: /etc/rc3.d/S20MyApp.sh { console | start | stop | restart |
> > condrestart | status | dump }
> > Legacy init script “/etc/rc3.d/S20MyApp.sh” exited with return code
> > 1.
> >
> > Why is the service control manager not passing the 'start' command to
> > my startup script?
> >
> > Thanks for you help,
> > Glenn
> >
> ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>