Sponsored Content
Full Discussion: Failed Write of utmpx entry
Operating Systems SCO Failed Write of utmpx entry Post 61551 by rm -r * on Friday 4th of February 2005 04:37:01 PM
Old 02-04-2005
The "i2" you see is the first two characters in the id of an inittab entry in the file /etc/inittab.

Per SCO's Technical Articles:

failed write of utmpx entry: xx

PROBLEM

The above error is known to happen when the init process is in the midst of creating an entry for the init job xx in the /etc/utmpx file, and gets interrupted by a SIGCLD signal, because some previously launched init job dies and needs to be cleaned up by init. Upon death of one of these child processes, the SIGCLD signal is generated and caught by init, which interrupts the current activity in order to perform the cleanup operation. Such "interruption" is usually normal. However, if a flurry of terminating init jobs happens at just the right time, the logging of another process by init in /etc/utmpx might fail with an internal error (i.e., "interrupted system call" or EINTR), and the console error shown above will appear. Of course, the end result is that the utmpx entry never gets logged.

SOLUTION

This problem has been reported to SCO Engineering. Currently, the workaround depends on the significance of the inittab entry in question and the impact of not recording the corresponding utmpx entry in /etc/utmpx:
1) if the inittab entry is configured by SCO by default, for example,


i2o1:23:once:/usr/sbin/i2otrans > /dev/console 2>&1


then you might simply remove the entry from inittab and the problem will disappear at the next reboot. In this example, the "i2otrans" job can usually be removed if you are not using an i2o-enhanced HBA. Make sure to make the appropriate omissions in /etc/conf/init.d as well, to prevent the inittab entry from reappearing upon the next kernel rebuild.
2) if the inittab entry must be retained, and the logging of the utmpx entry is also desired (e.g., if desired results from the "who" or "uptime" utilities require that proper utmpx logging by the targeted inittab entry occur) you might avoid the unfortunate timing window described above by simply moving the entry to a different location in the inittab file.

3) if the inittab entry must be retained but logging of the utmpx entry is not necessary, then nothing needs to be done. The occurrence of the console error message "failed to write utmpx entry" does not affect the proper startup of the system in any other way.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

No utmpx entry.

I am trying to set up a trust between two hosts and from another host to both by creating an /etc/hosts.equiv file on both. I am able to rsh to all but one host (and I am able to rsh from that host to the other). I receive the following error: No utmpx entry. You must exec "login" from the lowest... (1 Reply)
Discussion started by: 98_1LE
1 Replies

2. UNIX for Dummies Questions & Answers

/: write failed, file system full

Sun server 4 Getting message /: write failed, file system full. Okay so the problem seems obvious. The file system is full. This server is used for DNS and DHCP on a T1 connected WAN. I can't get it to quit displaying the same message as above, even when powered down and restarted. So... (1 Reply)
Discussion started by: lancest
1 Replies

3. UNIX for Advanced & Expert Users

shutting down 5.7 on Intel: failed to write of utmpx entry

When shutting down a freshly installed version of 5.7 on a Compaq server I get two messages: INIT: failed to write of utmpx entry: "s0" and: INIT: failed to write of utmpx entry: "fw" then I can continue with the shutdown. When I bring the system back up it has not saved any of my... (2 Replies)
Discussion started by: DarkLord
2 Replies

4. Programming

Whant to write an entry in /etc/passwd (putpwent)

Hi i try to use the function putpwent to write a simple entry in "/etc/passwd" putpwnet returns 0 as it works but notething writes to /etc/passwd. What have i missed? My os -------- root@nighter-laptop:/home/nighter/labb# uname -a Linux nighter-laptop 2.6.22-14-generic #1 SMP Sun Oct 14... (5 Replies)
Discussion started by: nighter
5 Replies

5. UNIX for Dummies Questions & Answers

no utmpx entry and other questions

I have recently been assigned to help maintain some testing software on two UNIX stations. The stations are connected to instruments that supply power, signals, and take measurements from a box. Both test stations are basically the same. I was given a crash course (read a little training) a couple... (18 Replies)
Discussion started by: bjstaff
18 Replies

6. UNIX for Advanced & Expert Users

write failed: Broken pipe

The "write failed: Broken pipe" message is reported by the file sending PC which run my writed network device driver while 500MB or 900MB is sended! What does the message mean? Does this mean there is a bug in my driver? li,kunlun (11 Replies)
Discussion started by: liklstar
11 Replies

7. Shell Programming and Scripting

How to write a new entry at the beginning of a log file instead of at the end?

Hi Ladies and Gents, Explanation of my question with an example: Let's consider the script: backup_every_hour.sh #!/bin/bash rsync -auv $dir $backup_dir >> backup_every_hour_script.log Each time this script is called there will be a new entry at the end of the file... (1 Reply)
Discussion started by: freddie50
1 Replies

8. Shell Programming and Scripting

How to avoid ssh :Write failed: Broken pipe?

Hello, I am trying to run some code on Matlab over ssh . The code takes around 5-6 hours to complete. so after giving the command to run it , I locked my machine and then went off to sleep at night, only to discover in the morning that I get this message : ...Code running, partial results... (1 Reply)
Discussion started by: ajayram
1 Replies

9. Shell Programming and Scripting

Write to 1 failed [No space left on device]

I am getting error in a shell script having a simple date command. Error is " write to 1 failed ". We saw that /tmp folder was 100% full. When we cleared some space in /tmp folder then script worked fine. Why does date command(or any other command) require space in /tmp folder? Which settings... (6 Replies)
Discussion started by: mahish20
6 Replies

10. How to Post in the The UNIX and Linux Forums

Help me, write a bash script to delete parent entry with all their child entry in LDAP UNIX server

Hi All, Please help me and guide me to write a bash/shell script on Linux box to delete parent entry with all their child entries. example: Parent is : ---------- dn: email=yogesh.kumar@wipro.com, o=wipro, o=in child is: ---------- dn: cn: yogesh kumar, email=yogesh.kumar@wipro.com,... (1 Reply)
Discussion started by: Chand
1 Replies
init(8) 						      System Manager's Manual							   init(8)

NAME
init - Process control initialization SYNOPSIS
/sbin/init [0123456789MmQqSs] DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in the inittab file. The init program reads and processes the entries in the inittab file. The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init that tell it which run level to change to. Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a message on the console stating the location of the virtual console. To change the run level, the user specifies either the 0, 2, 3, or s flag. For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to be handled for that level. Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi- ately reexamine the inittab file, invoke the init program with the q flag. FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from /etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter- minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single user state with only the essential kernel services. FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8) Calls: kill(2), reboot(2) Files: inittab(4) delim off init(8)
All times are GMT -4. The time now is 04:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy