Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I just have seen something in the warn log and I'm investigating. See the
detailed log:
Feb 12 12:26:54 nimrodel postfix/local[29204]: ED7FE86F23: to=<[EMAIL
PROTECTED]>, relay=local, delay=62, status=sent (delivered to command:
/usr/bin/procmail)
Feb 12 12:26:54 nimrodel postfix/smtpd[29128]: connect from localhost[127.0.0.1]
Feb 12 12:26:52 nimrodel postfix/smtpd[29126]: disconnect from
localhost[127.0.0.1]
Feb 12 12:26:52 nimrodel amavis[26348]: (26348-06-28) FWD via SMTP:
<opensuse-es+bounces-6521-robin.listas...
Notice the clock jumping back two whole seconds? Well, postfix gives notice:
Feb 12 12:26:52 nimrodel postfix/qmgr[4707]: warning: backward time jump
detected -- slewing clock
...
Feb 12 12:27:34 nimrodel postfix/qmgr[4707]: warning: backward time jump
recovered -- back to normality
Now, why did the clock jump back two whole seconds? Is postfix adjusting
the clock, or is it just noticing it? I'm using ntp, it shouldn't do that!
But it does. See the xntpd log:
12 Feb 03:02:53 ntpd[4635]: offset -0.003808 sec freq 10.337 ppm error 0.010344
poll 10
12 Feb 03:03:28 ntpd[4635]: synchronized to 193.127.101.30, stratum 2
Hi Carlos,
I wonder if what I am experiencing is in any way related to your situation.
Since installing 10.2 using the now 'default' ext3 file system (in
recent past versions always used reiserfs) I have been having problems
with either shutting down the system and/or booting 10.2.
When shutting down I would almost always be either returned to the login
screen (where you enter your username and password) or, the most
prevalent, I would end up I believe at level 3 command line prompt
(black screen background) and be asked to login as root by providing the
password. Here I would login and then run the 'shutdown' command to shut
down the computer. At other times 10.2 would either simply attempt the
shutdown but then 'lockup' and just keep running with Suse's opening
blue splash screen and I would have to press the 'big red button', or
10.2 would actually shutdown normally. Using the available ways of
shutdown/restarting made no difference (I recall someone stating that he
got the right result when he waited until the screen went into B/W mode
before pressing the Confirm (the shutdown) box).
At the other end, when starting the system there would be problems as
well and very often the only way I could start 10.2 was by booting from
the installation DVD because after switching on and going past grub's
menu 10.2 simply would not comptete the boot sequence - the splashscreen
would stay on with the little dots going round and round the geecko
graphic). The other way out of this situation that I took was to push
the reset button and this would *sometimes*, and with much time delay,
get 10.2 started.
I put up with this behaviour as being just an annoyance in 10.2 and
would disappear in 10.3 (or if I chose to reinstall 10.2 but this time
under reiserfs) until a couple of days ago - and this is where this may
be of relevance (at least I hope so because maybe both our troubles
would be solved).
What I did a couple of days ago was to run e2fsck on the 10.2 partition
- and I got the following error messages which I have never seen even
when using ext3 some years back:
Error message #1:
Superblock last mount time is in the future, Fix<y>?
Error message #2:
/dev/hda9 has gone 49709 days without being checked, check forced
[that's 136 years!]
After the above was repaired by e2fsck the system shutdown OK.
BUT, this morning....... I had the usual trouble of booting.
I did the e2fsck check and.... Error message #1 came up again (but not
#2). After the fs was repaired 10.2 booted without a hitch.
Just to allay what the state of the clock is, the system clock *is* set
to the correcttime and date and NTP runs everyday (and I also
occasionally run NTPDATE manually just to 'keep NTP honest').
If this is not somehow related to your situation perhaps you (or
someone) can offer a reason for Error #1 (and #2), how to avoid it, and
what else to check to see what is causing it.
Ciao.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
