Topic: INIT : id "nd" respawning too fast - disabling for

[Francis Van Peborgh]

Hello all,

Since I upgraded to 5.6 (and the 3 updates), and I always get the message

INIT : id "nd" respawning too fast - disabling for 5 minutes

this message appears during the boot process just after entering the non-interactive boot section, and then every few minutes on the admin console, overwriting the menu.

Ideas anyone ?


Thanks,


Francis

[Jens]

Not much help, I'm afraid, but I spent about a day trying to solve this error during a hardware upgrade and complete disk restore from a recent backup. I tried various things using Knoppix etc. but no go. I ended up doing a clean installation, restoring a desktop backup, and upgrading as needed. (Of course, I still had my production server running until the new machine was ready to take over).

Good luck, I hope you have a recent backup of your important data.

/Jens

[Damien Curtain]

Francis Van Peborgh wrote:
>
> Hello all,
>
> Since I upgraded to 5.6 (and the 3 updates), and I always get
> the message
>
> INIT : id "nd" respawning too fast - disabling for 5 minutes
>
> this message appears during the boot process just after
> entering the non-interactive boot section, and then every few
> minutes on the admin console, overwriting the menu.
>
> Ideas anyone ?

named is failing to start, thats your local dns server.

See if re-running the event /etc/e-smith/events/actions/named-conf solves your problem. It should log enough information to /var/log/messages to see why it's failing to start. Alternatively you can add something similar to the following template fragment to log to /home/dns/var/named/log/

/etc/e-smith/templates-custom/etc/named.conf/70logging
logging \{
        channel varlog \{
                file "log/named.log";
                severity notice;
                print-category yes;
                print-severity yes;
                print-time     yes;
        \};

        channel statslog \{
                file "log/stats.log" versions 2 size 128k;
                severity info;
                print-category no;
                print-severity no;
                print-time     yes;
        \};

        channel querylog \{
                file "log/query.log" versions 2 size 128k;
                severity debug;
                print-category no;
                print-severity no;
                print-time     yes;
        \};

        channel debuglog \{
                file "log/debug.log" versions 2 size 128k;
                severity dynamic;
                print-category yes;
                print-severity yes;
                print-time     yes;
        \};

        category default \{
                default_syslog;
                debuglog;
                varlog;
        \};

        category security \{
                debuglog;
                varlog;
        \};

        category db \{
                debuglog;
                varlog;
        \};

        category xfer-in \{
                debuglog;
                varlog;
        \};

        category xfer-out \{
                debuglog;
                varlog;
        \};

        category queries \{
                querylog;
        \};

        category lame-servers \{
                null;
        \};
\};

If you do this remember to make the directory /home/dns/var/named/log/
--
 Damien

[Gordon]

Francis
Did you find an answer to this problem. We also hav a server doing this since a user decided to press the reset button.
One other message we get on the console when we issue the command
service named status

rndc: connect failed
Has anyone else had this problem?
Many Thanks
Gordon

[Luis Francisco Ludovico]

I detect that primary domain (define en original setup) was added in virtual domains too.

I delete in virtual domain and correct this problem

I have added domains with LAT scripts..