This afternoon the maillog showed some wierd issues, and I could not get the mail through the POP3 server.
pam(dennis,192.16x.x.xx): PAM child process 7842 timed out, killing it
wb dovecot: auth(default): pam(dennis,192.16x.x.xx): Child process died
wb dovecot: auth(default): PAM: Child 7842 died with signal 9
Took me some time to find out that I had to recover a ‘database’ ? Finally this is the solution (CentOS / Bluequartz)
service dovecot stop
service xinetd stop
service admserv stop
killall -9 dovecot-auth
service admserv start
service xinetd start
service dovecot start
When my USB disk (used for the backup of my (this) server) is connected to the USB port and powered on the Linux CentOS server will not boot after the SELinux: unregistering netfilter hooks message.
When the USB disk is turned off: the server is booting normally and all services are started and everyone can surf onto my sites again, send e-mail etc..
What can be the reason why Linux is not booting properly when my USB disk is on?
Onboard SIS900 networkÂ card issue with Centos 4.4Â & Bluequartz andÂ no network activity available even when all config info says it is (with Linux version 2.6.9-42.0.2.EL). Problem found in disabled APM / ACPI. When disabled theÂ 2.6.9-42.0.2.EL will not be able to communicate through the network card. When enabling APM / ACPI it is.
This error was not seen when using Linux version 2.6.9-22.0.2.ELÂ
I removed all kernels in between and now CentOS together with my BlueQuartz services is running fine. Even when I will have a power shutdown again ;-) Enig klein probleem wat ik heel even tegen kwam, waren de 2 volgende meldingen:
SepÂ 6 19:26:49 wb kernel: CPU0: Running in modulated clock mode
SepÂ 6 19:26:54 wb kernel: CPU0: Temperature above threshold
Changed some BIOS settings this morning. Info of temperature is not measured. Maybe that’s a solution
Damn the xs4all time server 188.8.131.52 has some issues. It’s messing up the system time at my server. (and all my logfiles) .. Pffffffff. Removing it from webserver admin interface to see if problem is solved. If so than above IP is really making a mess of it
Problem of time @ server has to do with update CentoS (3.5) 4.3 to CentOS 4.4 when fully yum updated more BlueQuartz / CentOS users suffer from same issue. I changed Timezone setting to another timezone applying and then putting it back to the normal timezone. Let see if the logfile is giving me the correct time now.