[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Justin Willmert wrote:
Chris Jones wrote:
Justin Willmert wrote:
Chris Jones wrote:
Nicolas Mailhot wrote:
Le mercredi 19 juillet 2006 à 21:08 +0100, Chris Jones a écrit :
I have chosen to install amavis-new with my FC5 installation. This also loads clamav. However, when I look at the amavis service, I get the response "amavisd dead but subsys locked". I have checked everything I can think of, but cannot get amavisd to start. Does anyone here have any suggestions?
1. remove the dangling lock
2. start amavis
3. take a peek in /var/log/maillog
I looked for the dangling lock. However, I can find nothing. I would expect to find it (with amavisd running) at /var/run/amavisd/ along with the pid file, but there is nothing. Where else should I look?
Try looking in /var/lock/subsys.
I have tried that. I removed the hanging lock, which when checked, stopped amavisd. However, on starting amavisd, apparently successfully, after checking the status, amavisd was again dead but subsys locked.
I seem to be going around in circles. HOW do I correct this???

I guess next I'd suggest looking at the init.d file and seeing what it is doing. I do it sometimes when something isn't working right and try to recreate the steps by hand, seeing where it goes wrong. Sometimes it leads me to the problem area where I can finally get an idea of what should be changed.
Following your suggestion, I put the following commands through in a terminal session:-
[[email protected] init.d]# . /etc/rc.d/init.d//functions
[[email protected] init.d]# . /etc/sysconfig/network
[[email protected] init.d]# [ -e /etc/sysconfig/amavisd ] && . /etc/sysconfig/amavisd
[[email protected] init.d]# retval=0
[[email protected] init.d]# action $"Starting amavisd: " amavisd -c amavisd
Starting amavisd: Error reading config file "amavisd": No such file or directory at /usr/sbin/amavisd line 1205.
[1] 7929                                                   [FAILED]

[[email protected] init.d]# action $"Starting amavisd: " amavisd -c /etc/amavisd/amavisd.conf Starting amavisd: [1]+ Done [ -w /var/gdm/.gdmfifo ] && echo "BOOTUP_ERRORS" >/var/gdm/.gdmfifo
                                                          [  OK  ]
[[email protected] init.d]# retval=$?
[[email protected] init.d]# [ $retval -eq 0 ] && touch /var/lock/subsys/amavisd
[[email protected] init.d]# echo

[[email protected] init.d]# service amavisd status
amavisd (pid 7937 7936 7934) is running...
[[email protected] init.d]#


I am even more puzzled. The normal 'service amavisd start', 'service amavisd stop', and 'service amavisd restart' all fail for one reason or another, yet this technique seems to do the job.
--
Chris Jones



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]
  Powered by Linux