Frequent logouts from fc12 P4 machine
 

Hello,
I have a P4(R) Intel(R) 2.4 GHz CPU machine having 1 GB Ram on which I have loaded Fedora 12 (Constantine). This is a new assembled machine (3-4 months old now). The available free disk space is about 24 GB.

This machine works erratically in 2 respects:

1)It will work will for some time...In the sense it will allow me to login, work in eclipse, start tomcat etc and suddenly without warning it just sort of logs off and goes to the login console. Usually I login again and that takes cares of the problem for a few hours sometimes for a few days. Today however this was happening frequently every 2 hours ...Any idea why is this happening?
2)This machine till date has never logged out cleanly and I have NEVER been able to hibernate it. During shutdown process it goes through the entire process of shutting down but never shuts off completely ...It just gives the message “System shutdown” initially and after sometime say “System Halted”. I have to then physically put off the machine....Do you think that this erratic shutdown process (incomplete shutdown) is in someway responsible for the issues in 1.

I would appreciate very much if someone gives me a hint as to why the machine is frequently loging off recently. Do you think there is some issue with fc12 and that I should load fc13 ? Please advice urgently.

Regards

My first impression is that you have a hardware problem. You should look through the /var/log/messages file for errors.

The computer is probably not turning the power off my itself because you haven't loaded the acpi module or the acpi module is malfunctioning. It may be related to the other problem.

Look at the settings on the motherboard. Check to see if acpi and/or apm are enabled. My motherboard has separate settings for these similar functions. If they are off then turn them on.

Also, are you overclocking the CPU or RAM? That would definitely cause this kind of problem. (#1)

For similar reasons a faulty power supply could cause this kind of problem. (#1)

And check the power cable from the computer to the electrical outlet in the wall.

Hello,
Thanks for your reply. I will check the messages files for errors.That will help me a lot.
What you are saying makes sense however how does that explain that the computer works for days without any issues and then suddenly starts logging off every 30 minutes or so. For e.g the computer has worked correctly for the past 10 days inspite of working continuously on it for 8 hours a day and then yesterday the electric power supply went off...The UPS kicked in for about 20 minutes but the computer could not be shutdown properly as my CRT monitor was not on the UPS. As a result the computer just switched off when the UPS battery died.
After bringing up the computer it started giving all these problems.

Also I did not overclock the CPU or RAM...How do I find whether these components have been overclocked?

How do I look at the settings on the motherboard to see if acpi and/or apm are enabled? Is there a User Interface via the BIOS UI or can one look at it through some hardware diagnostic tool that comes inbuilt in Fedora?

In any ways I will check the messages file and get back to you. Thanks a lot for your very helpful pointers.



Regards

Hi,

i agree with stress_junkie. Definitely you should use a tool like memtest86 to check you memory. I had nearly the same behaviour on a laptop years ago, a memory module was the reason for the unexpected reboots.

Thanks for your replies...I will check it out.
But does Fedora itself not have any built applications to test the Hard disk, memory, or Motherboard etc...If there are can you let me know where it is...
Anyways thanks for the pointer.

Hi,

there is no possibility to test RAM from within a running operating system, so a program like memtest86 is required to do.

frequent logouts
 

Hello,
Based on your suggestions I did go through the messages log file but could not clearly understand what the problem is. FYI today the computer was working well from about 2 pm in the afternoon to about 6:15pm when all of a sudden it logged off. Please note it does not shut down but ONLY LOGS off...I wonder why this is happening...Please find attached the log file. Can some expert go throught this and let me know if I have an installation issue or a hardware issue....
Would appreciate some help and advise. PL. find some lines of the crash in this text ..but the actual crash log (part of it) is in the attachment.
Regards
=====================================


ec 10 14:12:30 localhost rtkit-daemon[1444]: Sucessfully made thread 1634 of process 1634 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Dec 10 14:12:30 localhost pulseaudio[1634]: pid.c: Daemon already running.
Dec 10 14:12:32 localhost restorecond: Unable to watch (/home/developer1/public_html/*) No such file or directory
Dec 10 18:12:01 localhost pulseaudio[1609]: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
Dec 10 18:12:01 localhost pulseaudio[1609]: alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_intel8x0'. Please report this issue to the ALSA developers.
Dec 10 18:12:01 localhost pulseaudio[1609]: alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Dec 10 18:29:33 localhost abrt: can not get proc info for pid 1371
Dec 10 18:29:33 localhost gnome-session[1473]: WARNING: Detected that screensaver has left the bus
Dec 10 18:29:33 localhost gnome-keyring-daemon[1465]: dbus failure unregistering from session: Connection is closed
Dec 10 18:29:33 localhost gnome-keyring-daemon[1465]: dbus failure unregistering from session: Connection is closed
Dec 10 18:29:33 localhost abrtd: Directory 'ccpp-1291985973-2138' creation detected
Dec 10 18:29:34 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1291985973-2138.lock' is locked by process 2962
Dec 10 18:29:34 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1291985973-2138.lock' is locked by process 2962
Dec 10 18:29:35 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1291985973-2138.lock' is locked by process 2962
Dec 10 18:29:35 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1291985973-2138.lock' is locked by process 2962
Dec 10 18:29:36 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1291985973-2138.lock' is locked by process 2962
Dec 10 18:29:36 localhost abrtd: Lock file '/var/cache/abrt/ccpp-1291985973-2138.lock' is locked by process 2962
D

the now unsupported & END OF LIFE fedora 12 never did - it never worked right

this might have been fixed in the CURRENT and SUPPORTED version of fedora
Fedora 14

Does that mean there is a problem with the installation and its not a hardware issue? I do not have fc14 downloaded...but have fc 13...DO you think fc13 will make this problem go away?
Also can someone give me a hint based on the error file that I have uploaded? Would appreciate some feedback on the error file..

Regards

at this time i am not running fedora 14 but the hibernation issues have been better worked out in the last year .
and fedora 13 and 14 are the only supported versions of fedora .

Thanks John...That was really useful information. I think I will take your advice and go in for a install of fc14.
Regards

Suddenly logging out and going to the login screen sounds like X crashing.

Still you should probably try Fedora 14 first.

Hello,
Thanks for your suggestion that the issue could be X server crashes. I had attached the messages log file when this issue occured and have also posted a few lines from the log file in one of my previous posts on this thread. Does the log file indicate X server crashes or some hardware issues.
Would appreciate some feedback if you have the time.
Anyways I thank you for your tip. I think it was helpful and relevant.
Regards