httpd and dovecot service start fails
Kevin Raber
ktr at mtu.edu
Mon Feb 6 05:13:36 UTC 2006
Harold Hallikainen wrote:
>> On Sun, Feb 05, 2006 at 01:53:38PM -0800, Harold Hallikainen wrote:
>>>> On Sat, Feb 04, 2006 at 09:43:02PM -0800, Harold Hallikainen wrote:
>>>>> I'm installing FC4 on an old machine after having success on a new
> machine. I did a new install (instead of update) and modified the
>>> same
>>>>> configs I modified on the new machine. Here's the latest problem.
>>> This
>>>>> is
>>>>> getting real close to working correctly!
>>>>>
>>>>> If I do /sbin/service httpd restart or /sbin/service dovecot
> restart,
>>>>> the
>>>>> restart fails (the stop fails too since they did not start properly
> during
>>>>> boot). However, if I do /usr/sbin/httpd or /usr/sbin/dovecot , they
>>> both
>>>>> seem to run fine. How can I find out what's going wrong during boot
>>> or
>>>>> restart that's causing these to not run? I've looked in the httpd
>>> logs
>>>>> and
>>>>> the messages log and found nothing.
>>>> Look again. For httpd, look in /var/log/httpd/error_log. For
> dovecot, look in /var/log/maillog. If a service isn't starting
> properly, there _must_ be some information either on the screen or in
> a log.
>>> I left httpd running last night by manually starting it. I then did a
> service httpd restart this afternoon. Here's the restart:
>>> [root at kauko sbin]# ./service httpd restart
>>> Stopping httpd: [ OK ]
> Starting httpd: [FAILED]
> [root at kauko sbin]#
>>> And here's the error_log:
>>> [Sun Feb 05 04:02:20 2006] [notice] Digest: generating secret for
> digest
>>> authentication ...
>>> [Sun Feb 05 04:02:20 2006] [notice] Digest: done
>>> [Sun Feb 05 04:02:20 2006] [notice] LDAP: Built with OpenLDAP LDAP SDK
> [Sun Feb 05 04:02:20 2006] [notice] LDAP: SSL support unavailable [Sun
> Feb 05 04:02:22 2006] [notice] mod_python: Creating 4 session mutexes
>>> based on 150 max processes and 0 max threads.
>>> [Sun Feb 05 04:02:23 2006] [notice] Apache/2.0.54 (Fedora) configured
> --
>>> resuming normal operations
>>> [Sun Feb 05 13:49:44 2006] [notice] caught SIGTERM, shutting down
> Waiting for data... (interrupt to abort)
>>> The 13:49:44 appeared when I did the restart. Nothing appeared after
> that...
>>> THANKS!
>>> Harold
>> Hmm. This does not compute. Try to start it again, and very soon
> after, do this:
>> cd /var/log
>> ls -lrt
>>
>> The last log touched will be at the bottom of the list. My guess is it
> will be messages. Check that. Also check
>> /var/log/httpd/access_log. It must be leaving a suicide note somewhere.
>>
>
>
> OK, here it is...
>
> [root at kauko squirrelmail]# /sbin/service httpd restart
> Stopping httpd: [ OK ]
> Starting httpd: [FAILED]
> [root at kauko squirrelmail]# cd /var
> [root at kauko var]# ls -lrt
> total 204
> drwxr-xr-x 2 root root 4096 Mar 28 2005 racoon
> drwx------ 2 root root 4096 Apr 20 2005 tux
> drwxr-xr-x 2 root root 4096 Apr 20 2005 cvs
> drwxr-xr-x 2 root root 4096 May 22 2005 preserve
> drwxr-xr-x 2 root root 4096 May 22 2005 opt
> drwxr-xr-x 2 root root 4096 May 22 2005 nis
> drwxr-xr-x 2 root root 4096 May 22 2005 local
> lrwxrwxrwx 1 root root 10 Jan 7 18:17 mail -> spool/mail
> drwxr-xr-x 3 root root 4096 Jan 7 18:24 db
> drwxr-xr-x 2 root root 4096 Jan 7 18:24 account
> drwxr-xr-x 3 root root 4096 Jan 7 18:25 empty
> drwxr-x--- 5 root named 4096 Jan 7 20:30 named
> drwxr-xr-x 3 root root 4096 Jan 7 20:39 ftp
> drwxr-xr-x 3 root root 4096 Jan 7 20:52 kerberos
> drwxr-xr-x 5 netdump netdump 4096 Jan 7 20:52 crash
> drwxr-xr-x 3 root root 4096 Jan 7 20:53 yp
> drwxr-xr-x 11 root root 4096 Jan 7 22:30 cache
> drwxr-xr-x 2 pcap pcap 4096 Jan 7 22:44 arpwatch
> drwxr-xr-x 25 root root 4096 Jan 7 22:52 spool
> drwxr-xr-x 11 root root 4096 Jan 7 22:52 www
> drwxr-xr-x 35 root root 4096 Jan 8 14:17 lib
> drwxrwxr-x 8 root lock 4096 Feb 5 18:16 lock
> drwxr-xr-x 24 root root 4096 Feb 5 18:17 log
> drwxrwx--T 2 root gdm 4096 Feb 5 18:17 gdm
> drwxrwxrwt 2 root root 4096 Feb 5 18:28 tmp
> drwxr-xr-x 30 root root 4096 Feb 5 20:55 run
> [root at kauko var]#
>
>
> I ran the restart at 20:55. Looking in run, I see this:
>
> [root at kauko var]# cd run
> [root at kauko run]# ls -lrt
> total 412
> drwxr-xr-x 2 root root 4096 Nov 2 2004 ppp
> drwxr-xr-x 2 radvd radvd 4096 Feb 25 2005 radvd
> drwxrwsr-x 2 root mailman 4096 Mar 7 2005 mailman
> drwxr-xr-x 2 pvm pvm 4096 Mar 8 2005 pvm3
> drwxrwx--x 2 quagga quagga 4096 Apr 4 2005 quagga
> drwxr-x--- 2 news news 4096 Apr 7 2005 news
> drwxr-xr-x 2 root root 4096 Apr 13 2005 saslauthd
> drwx------ 2 radiusd radiusd 4096 Apr 14 2005 radiusd
> drwx------ 2 root root 4096 Apr 27 2005 pluto
> drwxr-xr-x 2 root root 4096 May 2 2005 winbindd
> drwx------ 2 root root 4096 May 16 2005 mdmpd
> drwx------ 2 root root 4096 May 16 2005 mdadm
> drwxrwx--- 2 named named 4096 May 17 2005 named
> drwx------ 2 root root 4096 May 18 2005 iptraf
> drwx------ 2 root root 4096 May 23 2005 usb
> drwxrwxr-x 2 root root 4096 May 25 2005 netreport
> drwxrwxr-x 2 root screen 4096 May 27 2005 screen
> drwxr-xr-x 2 root root 4096 May 30 2005 nscd
> drwx------ 4 root root 4096 Jan 8 14:52 sudo
> drwxr-xr-x 2 root root 4096 Feb 4 16:53 ptal-printd
> drwxr-xr-x 2 root root 4096 Feb 4 16:53 ptal-mlcd
> drwxr-xr-x 2 root root 4096 Feb 4 16:59 console
> -rw------- 1 root root 5 Feb 5 18:16 syslogd.pid
> -rw-r--r-- 1 rpcuser rpcuser 5 Feb 5 18:16 rpc.statd.pid
> -rw------- 1 root root 5 Feb 5 18:16 klogd.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 irqbalance.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 auditd.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 nifd.pid
> -rw-r--r-- 1 nobody root 5 Feb 5 18:16 mDNSResponder.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 xinetd.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 sshd.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 cupsd.pid
> -rw-r--r-- 1 root root 4 Feb 5 18:16 ntpd.pid
> drwxr-xr-x 2 mysql mysql 4096 Feb 5 18:16 mysqld
> -rw------- 1 root smmsp 33 Feb 5 18:16 sendmail.pid
> -rw-r--r-- 1 smmsp smmsp 50 Feb 5 18:16 sm-client.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 gpm.pid
> drwxr-xr-x 3 iiimd iiimd 4096 Feb 5 18:16 iiim
> -rw-r--r-- 1 root root 5 Feb 5 18:16 crond.pid
> -rw-r--r-- 1 root root 6 Feb 5 18:16 xfs.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 smbd.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 nmbd.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 messagebus.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 haldaemon.pid
> drwxr-xr-x 2 root root 4096 Feb 5 18:16 dbus
> -rw-r--r-- 1 root root 5 Feb 5 18:16 cups-config-daemon.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:16 atd.pid
> -rw-r--r-- 1 root root 5 Feb 5 18:17 gdm.pid
> -rw-rw-r-- 1 root utmp 4608 Feb 5 18:17 utmp
> drwx------ 2 root root 4096 Feb 5 18:20 dovecot
> drwxr-x--- 2 root dovecot 4096 Feb 5 18:20 dovecot-login
> [root at kauko run]#
>
>
> So.... I don't see any log entry... Ideas?
>
>
> THANKS!
>
> Harold
>
>
Harlod,
I believe the request was for:
cd /var/log
ls -lrt
More information about the Redhat-install-list
mailing list