INIT: failed write of utmpx entry: s0

INIT: failed write of utmpx entry: s0

Post by RFarley2 » Sun, 29 Dec 1996 04:00:00



Upon doing a 'shutdown -y g0 -0'  on a Sparc 5
running Solaris 2.5 and CDE, I get the following
........................................................................
<nodename> syslogd: going down on signal 15
nfs umount:  <nodename>: vold (PID) server not responding:
RPC: Program not registered

/usr/sbin/vold[PID]:  problem unmounting /vol; Interrupted system
call
The system is down.

INIT:  failed write of utmpx entry: "s0"
INIT:  failed write of utmpx entry: "fw"
syncing file systems.....[9] [5] done
Program terminated
OK
..........................................................................
............

This is a standalone machine with no NFS mounts going at the time.

Which RPC program is the error refering to as 'not registered' and why?
What are the s0 and fw entries in utmp?
Can anything be done to alleviate these errors?  We've tried adding
a sleep 10 in the /etc/init.d/volmgt script after the kill line.  We have
also tried a grace period of 10 on the shutdown, no luck.

Thanks


 
 
 

INIT: failed write of utmpx entry: s0

Post by Casper H.S. Dik - Network Security Engine » Sun, 29 Dec 1996 04:00:00



>nfs umount:  <nodename>: vold (PID) server not responding:
>RPC: Program not registered
>/usr/sbin/vold[PID]:  problem unmounting /vol; Interrupted system
>call
>The system is down.
>INIT:  failed write of utmpx entry: "s0"
>INIT:  failed write of utmpx entry: "fw"
>syncing file systems.....[9] [5] done
>Program terminated
>OK
>..........................................................................
>............

The first message appear because you dont' export any NFS filesystems;
they don't appear on an NFS server.
I always see the second too, don't know how to prevent that.

And on the INIT: message, the FAQ says:

5.52) When I halt/reboot my system I get "INIT: failed write of utmpx entry"

    When the system shuts down, init(1m) updates /var/adm/utmp* to
    reflect that fact.

    If you have a separate /var filesystem, this operation will happen
    *after* /var is unmounted and init complains:

    INIT: failed write of utmpx entry:"s6"
    INIT: failed write of utmpx entry:"rb"

    You can safely ignore these messages.

    --- end of excerpt from the FAQ

Questions marked with a * or + have been changed or added since
the FAQ was last posted

The most recently posted version of the FAQ is available from
<http://www.fwi.uva.nl/pub/solaris/solaris2/>

--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

INIT: failed write of utmpx entry: s0

Post by Casper H.S. Dik - Network Security Engine » Mon, 30 Dec 1996 04:00:00



>nfs umount:  <nodename>: vold (PID) server not responding:
>RPC: Program not registered
>/usr/sbin/vold[PID]:  problem unmounting /vol; Interrupted system
>call
>The system is down.
>INIT:  failed write of utmpx entry: "s0"
>INIT:  failed write of utmpx entry: "fw"
>syncing file systems.....[9] [5] done
>Program terminated
>OK
>..........................................................................
>............

The first message appear because you dont' export any NFS filesystems;
they don't appear on an NFS server.
I always see the second too, don't know how to prevent that.

And on the INIT: message, the FAQ says:

5.52) When I halt/reboot my system I get "INIT: failed write of utmpx entry"

    When the system shuts down, init(1m) updates /var/adm/utmp* to
    reflect that fact.

    If you have a separate /var filesystem, this operation will happen
    *after* /var is unmounted and init complains:

    INIT: failed write of utmpx entry:"s6"
    INIT: failed write of utmpx entry:"rb"

    You can safely ignore these messages.

    --- end of excerpt from the FAQ

Questions marked with a * or + have been changed or added since
the FAQ was last posted

The most recently posted version of the FAQ is available from
<http://www.fwi.uva.nl/pub/solaris/solaris2/>

--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

INIT: failed write of utmpx entry: s0

Post by John Theobal » Mon, 30 Dec 1996 04:00:00



> Upon doing a 'shutdown -y g0 -0'  on a Sparc 5
> running Solaris 2.5 and CDE, I get the following
> ........................................................................
> <nodename> syslogd: going down on signal 15
> nfs umount:  <nodename>: vold (PID) server not responding:
> RPC: Program not registered

> /usr/sbin/vold[PID]:  problem unmounting /vol; Interrupted system
> call
> The system is down.

> INIT:  failed write of utmpx entry: "s0"
> INIT:  failed write of utmpx entry: "fw"
> syncing file systems.....[9] [5] done
> Program terminated
> OK
> ..........................................................................
> ............

> This is a standalone machine with no NFS mounts going at the time.

> Which RPC program is the error refering to as 'not registered' and why?
> What are the s0 and fw entries in utmp?
> Can anything be done to alleviate these errors?  We've tried adding
> a sleep 10 in the /etc/init.d/volmgt script after the kill line.  We have
> also tried a grace period of 10 on the shutdown, no luck.

> Thanks



Just to augment what Casper indicated in his response ...

As for the "second" message regarding vold, I don't know why Sun has
never fixed this but you can eliminate these vold related messages
during shutdowns and init transitions by simply creating a link from
/etc/init.d/volmgt to /etc/rc0.d/K02volmgt.

For whatever reason Sun has not created an explicit kill for vold.

Just my two cents...

John Theobald
Sun Educational Services
Atlanta, GA.

 
 
 

1. INIT: failed write of utmpx entry:"s0"

I have seen these messages a lot of times on a lot of systems
since Solaris 2.3, but never on my own ones, until now:

    INIT: failed write of utmpx entry:"s0"
    INIT: failed write of utmpx entry:"fw"

So what do they mean? I recently moved the /var directory tree
into its own partition, can this be the cause?

Arndt

(The messages are printed each time the system ist brought
down with `init 0'. They follow the message `The system is
down.' and precede the `syncing file systems... [11] [8] [3]
done'. The system in question runs Solaris 2.5 x86.)

2. ftp not working

3. INIT: failed write of utmpx entry: "s0"

4. Crystal CS4236 sound card trouble

5. failed write of utmpx entry : "s0"

6. modem configuration question

7. INIT: failed write of utmpx entry:" "

8. DPT Driver crashes.

9. INIT: failed to write utmpx "

10. utmpx entry failed after Solaris 2.6 installation on Ultra 1

11. failed write of utmpx

12. Failed to write utmpx

13. failed write utmpx