Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: nss started too late in squence-mysql fails

8 views
Skip to first unread message

jmcg

unread,
Jan 19, 2010, 6:08:55 PM1/19/10
to
brunold,
This mysql is set up without using any of the script that you pasted in your
reply. I am asumming that if I change the script that I would remove the #
signs, that I am assuming comment out that part of the script. Is that
correct, or do I leave the # signs in place.

Thank you for the quick reply.

"brunold" <bru...@no-mx.forums.novell.com> wrote in message
news:brunold...@no-mx.forums.novell.com...
>
> jmcg,
>
> reordering is not the best way to do this because is is just a
> temporary solution (that might not have worked for you).
>
> The startup order is calculated based on the LSB header in the runlevel
> scripts in /etc/init.d when they got activated for automatically
> startup. The LSB header contains some "Required" and "Provides" sections
> which are use to calculate the startup order. So you should adopt that
> LSB header - "Required" line to contain novell-nss in the mysql file
> like this:
>
>
> Code:
> --------------------
> # cat /etc/init.d/mysql
> ...
> ### BEGIN INIT INFO
> # Provides: mysql
> # Required-Start: $network $remote_fs *_novell-nss_*
> # Required-Stop:
> # Default-Start: 2 3 5
> # Default-Stop:
> # Description: Start the MySQL database server
> ### END INIT INFO
> ...
> --------------------
>
>
>
> Then use yast to disable mysql for automatically startup (or do it via
> the command line) and reinsert it. Then the startup order for this mysql
> script is calculated newly and it should be palced in the correct
> order.
>
> Command line:
>
> # insserv -r mysql
> # insserv mysql
>
> Please take in mind that mysql updates might overwrite this runlevel
> script and you might adopt it then another time.
>
> Rainer
>
>
> --
> brunold
> ------------------------------------------------------------------------
> brunold's Profile: http://forums.novell.com/member.php?userid=562
> View this thread: http://forums.novell.com/showthread.php?t=398698
>


jmcg

unread,
Feb 9, 2010, 3:15:04 PM2/9/10
to
You must still be busy. I am hoping that you will get a chance to look at
this and give some more advice. I appreciate your help.

"brunold" <bru...@no-mx.forums.novell.com> wrote in message
news:brunold...@no-mx.forums.novell.com...
>

> jncg,
>
> sorry I'm a little bit bussy at the moment because I need to prepare a
> workshop. Therefor I took some time to respond.
> From what I can see from your boot.msg is that mysql is still started
> before nss gets started.
>
> I can see that the mysql runlevel script is okay and contains the
> novell-nss and namcd, but I guess it is still placed incorrectly in the
> runlevel order.
>
> I assume you start always in runlevel 5 as I see that at the end of the
> boot.msg, therefor we check that directory.
>
> # ls /etc/init.d/rc5.d/*novell-nss
> # ls /etc/init.d/rc5.d/*mysql
> # ls /etc/init.d/rc5.d/*namcd
>
> The numbers of novell-nss and namcd must be lower then the one from the
> mysql.
>
> If that is not correct, remove it from automatically startup and
> reinsert it with:


>
> # insserv -r mysql
> # insserv mysql
>

> and then check the 3 ls commands once again and see if the order has
> changed.
>
> if not, please post the contents of the /etc/init.d/rc5.d:
>
> # ls /etc/init.d/rc5.d

jmcg

unread,
Feb 18, 2010, 11:34:53 AM2/18/10
to
SVUSD1:~ # runlevel
N 5
SVUSD1:~ # chkconfig -l | grep -e "^m" -e "^n"
mdadmd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
micasad 0:off 1:on 2:on 3:on 4:off 5:on 6:off
microcode 0:off 1:on 2:on 3:on 4:off 5:on 6:off
S:on
multipathd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
mysql 0:off 1:off 2:off 3:off 4:off 5:off 6:off
namcd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
named 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ncp2nss 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ndsd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
ndssnmpsa 0:off 1:off 2:off 3:off 4:off 5:off 6:off
network 0:off 1:off 2:on 3:on 4:off 5:on 6:off
nfs 0:off 1:off 2:off 3:on 4:off 5:on 6:off
nfsboot 0:off 1:off 2:off 3:on 4:off 5:on 6:off
nfsserver 0:off 1:off 2:off 3:off 4:off 5:off 6:off
nldap 0:off 1:off 2:off 3:off 4:off 5:off 6:off
nmb 0:off 1:off 2:off 3:off 4:off 5:off 6:off
novell-afptcpd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
novell-dfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
novell-httpstkd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
novell-idsd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
novell-ipsmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
novell-named 0:off 1:off 2:off 3:on 4:off 5:on 6:off
novell-nss 0:off 1:on 2:on 3:on 4:off 5:on 6:off
novell-shadowfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
novell-smdrd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
novell-tomcat5 0:off 1:off 2:off 3:on 4:off 5:on 6:off
novell-xregd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
novell-xsrvd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
novell-zmd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
nscd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ntp 0:off 1:off 2:on 3:on 4:off 5:on 6:off
SVUSD1:~ #

"brunold" <bru...@no-mx.forums.novell.com> wrote in message
news:brunold...@no-mx.forums.novell.com...
>
> Sorry still a little bit busy here, but lets bring it to a quick end
> ..
>
> The insserv error would tell that the required service novell-nss that
> we added to the REQUIRED section is not already activated. On the other
> side we see that there are links available in the rc5.d directory.
>
> In what runlevel is your system running ?
>
> # runlevel
>
> I would then check the status of the novell-nss, mysql and namcd
> runlevel scripts to see in what runlevels they are activate. For a
> listing of all m and n service via command line you can use:
>
> # chkconfig -l | grep -e "^m" -e "^n"
>
> Can you post that as well ?
0 new messages