Strange thing today, one of my old OpenBSD did a reboot.

If it was a hard reset (ie power problem) I wouldn't have a
wtmp record right?

# last
root      ttyp0    client.host    Mon Mar 15 16:47   still logged in
root      ttyp0    client.host    Mon Mar 15 16:26 - 16:27  (00:00)
reboot    ~                                 Mon Mar 15 09:46

wtmp begins Mon Mar 15 09:46 2010


Mar 15 07:54:12 server ntpd[5706]: adjusting local clock by 0.061002s
Mar 15 08:44:43 server ntpd[3592]: reply from 10.0.0.1: not synced (alarm), next query 3299s
Mar 15 09:46:03 server syslogd: start
Mar 15 09:46:03 server /bsd:       Processor Machine Check (670), Code 0x92
Mar 15 09:46:03 server /bsd: [ using 617920 bytes of bsd ELF symbol table ]
Mar 15 09:46:03 server /bsd: consinit: not using prom console
Mar 15 09:46:03 server /bsd: Copyright (c) 1982, 1986, 1989, 1991, 1993
Mar 15 09:46:03 server /bsd: The Regents of the University of California. All rights reserved. Mar 15 09:46:03 server /bsd: Copyright (c) 1995-2009 OpenBSD. All rights reserved. http://www.OpenBSD.org Mar 15 09:46:04 server /bsd: Copyright (c) 1995-2009 OpenBSD. All rights reserved. http://www.OpenBSD.org Mar 15 09:46:04 server /bsd: OpenBSD 4.6-stable (GENERIC) #3: Thu Nov 26 14:54:22 EET 2009 Mar 15 09:46:04 server /bsd: r...@server:/usr/src/sys/arch/alpha/compile/GENERIC
Mar 15 09:46:04 server /bsd: AlphaServer 400 4/233, 233MHz
Mar 15 09:46:04 server /bsd: 8192 byte page size, 1 processor.
Mar 15 09:46:04 server /bsd: real mem = 67108864 (64MB)
Mar 15 09:46:04 server /bsd: rsvd mem = 2048000 (1MB)
Mar 15 09:46:04 server /bsd: avail mem = 55369728 (52MB)
Mar 15 09:46:04 server /bsd: mainbus0 at root
Mar 15 09:46:04 server /bsd: cpu0 at mainbus0: ID 0 (primary), 21064A-0 (unknown minor type 0) Mar 15 09:46:04 server /bsd: apecs0 at mainbus0: DECchip 21071 Core Logic chipset

bla bla

Mar 15 09:46:05 server /bsd: WARNING: / was not properly unmounted
Mar 15 09:46:05 server /bsd: WARNING: clock gained 26 days -- CHECK AND RESET THE DATE!
Mar 15 09:51:20 server ntpd[6080]: 0 out of 1 peers valid
Mar 15 09:51:20 server ntpd[6080]: bad peer 10.0.0.1 (10.0.0.1)
Mar 15 09:51:40 server ntpd[6080]: peer 10.0.0.1 now valid
Mar 15 09:52:33 server ntpd[29796]: adjusting local clock by -55.558227s
Mar 15 09:55:14 server ntpd[29796]: adjusting local clock by -54.760153s
Mar 15 12:50:56 server ntpd[29796]: adjusting local clock by -1.665123s
Mar 15 12:53:33 server ntpd[29796]: adjusting local clock by -0.879955s
Mar 15 12:56:49 server ntpd[6080]: clock is now synced


ideas?

Giannis

Reply via email to