Topic: Server bouncing emails and unable to send from Horde- can send/receive locally.

[ber]

Hi Anthony, ran the script here is the output- no such file- any ideas?


[root@server ~]# rm /var/run/yum.pid
rm: cannot lstat `/var/run/yum.pid': No such file or directory
[root@server ~]# ls /var/run/
acpid.socket            httpd.pid         netreport  sme7admin.pid
clamav                  httpd.scoreboard  nmbd.pid   snmpd
console                 iptraf            nut        sshd.pid
crond.pid               klogd.pid         openldap   sudo
cron.reboot             lpd.515           ppp        syslogd.pid
dbus                    lprng             pptpd.pid  usb
dovecot                 mdadm             proftpd    utmp
haldaemon.pid           mdmpd             radiusd    winbindd
httpd-admin.pid         messagebus.pid    saslauthd
httpd-admin.scoreboard  mysqld            smbd.pid
[root@server ~]#

[kryptos]

I have finished update clamav to new version and do a signal-event post-upgrade and reboot. But I have error starting clamav deamon. See error below

Code: [Select]

Starting Clam AntiVirus Daemon: WARNING: Ignoring deprecated option ArchiveBlockMax at line 12
WARNING: Ignoring deprecated option ArchiveMaxCompressionRatio at line 13
ERROR: Parse error at line 14: Unknown option ArchiveMaxFileSize
ERROR: Can't open/parse the config file /etc/clamd.conf

I'm still using 7.3 but im afraid to upgrade to 7.4 right now. I have many setup made to this server so upgrading is not yet possible for me.  Based from the error I think there something need to commented on the /etc/clamd.conf but I don't know what will be the code of the template I will put. Anyone please advise.


P.S I try to update smeserver-clamav but I  have error missing dependency on Whiptail.

Regards,
Rocel

[agodin]

Ber's issue was to do with one of the sme-update repositories being disabled for yum updates - once this was enabled was then able to update to the latest ClamAV and db versions  0.95.3/10751/Fri Apr 16 11:23:45 2010

Bit odd as some of the systems we have dealt with today have regular updates, including one that was fully updated this morning but we had to do the clamav update manually to get it all going again.

Hope this helps others

Cheers
Anthony Godin

[jmvelez]

Clamav .94 End of Life yesterday (April 15, 2010 check it at http://www.clamav.net/).  You need  to update Clamav using YUM

[jonroberts]

Had the same problem on 4 servers.  The update fixed three, but still have one reporting problems.  Its SME 7.4, but has been recently upgraded from a 6x. 

I realise now that it had the ClamAV contrib installed & so Server Manager has two antivirus panels (the old & the new).  I suspect this may be the cause of the problem.

I've tried uninstalling it but without success so not sure I've done it correctly.  Is there a way I can completely uninstall Clam, including both the pre-installed SME7.4 and any parts of the previous contrib that may still be around and then download & re-install just the current version?

[Stefano]

hi..

first of all recover all the involved rpms with:

Code: [Select]

rpm -qa | grep clam
rpm -qa | grep virus

then remove it with

Code: [Select]

rpm -e --nodeps smeserver-clamav sme-antivirus clamd clamav clamav-db

the above list should work

then

Code: [Select]

yum install smeserver-clamav
signal-event post-upgrade
signal-event reboot

should work

HTH

[mmccarn]

It's OK to delete the yum.pid when you get this message 'Existing lock /var/run/yum.pid: another copy is running. Aborting.' if you have rebooted, as you know there cannot be a yum process running still

The SME "local" event (which is run at the end of the every reboot) runs yum in order to update the list of available packages in server-manager. 

As you know, yum is also run at other times for the same purpose:
http://wiki.contribs.org/Updating_from_SME_7.1.x_or_earlier#Existing_lock_.2Fvar.2Frun.2Fyum.pid:_another_copy_is_running._Aborting.

I don't know whether or not removing the lock file and re-running yum will damage anything, but on my medium-slow SME server if I wait 2 - 5 minutes the lock file goes away and yum works fine.

[CharlieBrady]

It's OK to delete the yum.pid when you get this message 'Existing lock /var/run/yum.pid: another copy is running. Aborting.'

No, it is not OK to do that.

if you have rebooted, as you know there cannot be a yum process running still

That is also untrue, as yum is run during normal startup.

[jonroberts]

Stefano - thanks for the tip, but after running an update the server failed to boot so I think there's a hardware problem, probably disk.  I was trying to sort the problem remotely, but will now visit the site to sort. 

[Stefano]

Stefano - thanks for the tip, but after running an update the server failed to boot so I think there's a hardware problem, probably disk.  I was trying to sort the problem remotely, but will now visit the site to sort. 

please report any problem (not hardware ) in bugzilla, thank you

[cactus]

It's OK to delete the yum.pid when you get this message 'Existing lock /var/run/yum.pid: another copy is running. Aborting.' if you have rebooted, as you know there cannot be a yum process running still

No it isn't. Another yum process is actually running, even after a reboot as a check for updates is performed at that moment (as well), which is why yum is locked. Wait a few minutes and then retry, killing yum is not the proper solution.

[CharlieBrady]

Hi a desperate post regarding My SME 7.4 server- been running well now rejecting emails ...

You should double check whether that is true or not. If clamav is down, your server should only be deferring email messages, not rejecting them. They will arrive a little later, after you have fixed the problem.

[ber]

Hi I just want to say thank you for all the helpful response to my post and even Anthony's helpful follow-up phone call!! JUST AWESOME.
As he mentioned it turned out to be clamv program being out of date due to my sme repository's not being setup properly. Thanks again- look forward to when i can be a helpful contributer to someone who needs help. Still learning and enjoying the ride.

Regards John Henry

[MSmith]

One server that had been running faithfully for years stopped sending/receiving emails even locally, and would not do so until virus scanning was disabled.  Server was updated, same result.  However, I should note that this machine is a 500 MHz Athlon with 512 megs of RAM so I am thinking the hardware just isn't up to the task.  I've ordered a replacement machine (2 GHz Xeon, 2 gigs RAM) and will do the usual Affa replacement and am hoping that'll take care of the problem.

[johnp]

One server that had been running faithfully for years stopped sending/receiving emails even locally, and would not do so until virus scanning was disabled.  Server was updated, same result.  However, I should note that this machine is a 500 MHz Athlon with 512 megs of RAM so I am thinking the hardware just isn't up to the task.  I've ordered a replacement machine (2 GHz Xeon, 2 gigs RAM) and will do the usual Affa replacement and am hoping that'll take care of the problem.

I think you should raise a bug report.