Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

uptime 13XXX days

Status
Not open for further replies.

unixfreak

ISP
Oct 4, 2003
632
GB

Odd thing, all the server on a p570 has the uptime as 13670-something days. I just cloned a server and it's been up since Friday but that's also showing 13670 days.

Where does a partition get it's time from and is this uptime thing a known bug?

Thanks
 
I believe it's held in /etc/utmp. Try strings /etc/utmp to view.

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."
 
That is close to the number of days since 1st Jan 1970, what is the system / FSP time?

Did you install the node as 1st Jan 1970 and then set the time / date?

Just an idea to consider.
 
Ihad this on one of my servers and found that it was ecause /etc/utmp was being cleared down in a cron
 

Hi, there's no time setting in the ASM other than current time of the day. No year or anything.

I deleted /etc/utmp off one of the servers and that fixed it. Will need to do the others but I don't know how it got into that state

Thanks
 
What version on AIX, I seem to remember a bug in the past after a certain number of days up.

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."
 
To start with I would take your server to the next CSP, but to find out what corrupted utmp try the following (if it happens again)

Code:
To correct the invalid boot time you must reboot the system. The utmp file is recreated with each boot.

To attempt to discover who or what overwrote the first entry in the file, use the following command to create a readable version of the utmp file and look at record 0:

NOTE: The fwtmp command must first be installed. For AIX Version 4, install bos.acct.

/usr/sbin/acct/fwtmp < /etc/utmp  >/tmp/out
A valid entry looks something like this:

system boot 0 2 0000 0000 818538505 Sat Dec 9 13:48:25 CST 1995
Instead of the system boot entry, you will probably find an entry like:

jones pts/2 19193 7 0000 0000 818683926 Mon Dec 11 06:12:06 CST 1995
This output means that the time stamp was corrupted by whatever program jones on pts/2 used to login. A program should never overwrite the first two entries in the utmp file. You would have to talk with jones to see what he did. This is almost always caused by a third party program that is incorrectly writing to the utmp file or a corrupted file system where the data is invalid.

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top