Fixing the “No updates detected in the log for the freshclam daemon” error

Have been banging my head on this for a while now. Logwatch kept reporting in his daily summary something along the lines of what below:

——————— clam-update Begin ————————

No updates detected in the log for the freshclam daemon (the
ClamAV update process). If the freshclam daemon is not running,
you may need to restart it. Other options:

A. If you no longer wish to run freshclam, deleting the log file
(default is freshclam.log) will suppress this error message.

B. If you use a different log file, update the appropriate
configuration file. For example:
echo “LogFile = log_file” >> /etc/logwatch/conf/logfiles/clam-update.conf
where log_file is the filename of the freshclam log file.

C. If you are logging using syslog, you need to indicate that your
log file uses the syslog format. For example:
echo “*OnlyService = freshclam” >> /etc/logwatch/conf/logfiles/clam-update.conf
echo “*RemoveHeaders” >> /etc/logwatch/conf/logfiles/clam-update.conf

———————- clam-update End ————————-

suggesting that either clam-update was not running or the log file location was misconfigured.

Checked all that a number of times, made sure the permissions were correct, no difference.

Finally I realized that there is an error in the date detection of the freshclam related script which comes with Logwatch 7.3.6, and the solution comes down to editing the file:

/usr/share/logwatch/scripts/services/clam-update

and at around line 89 (this on CentOS 6.5) replace:
$ThisLine =~ s/ $//;

with
$ThisLine = substr($ThisLine, 28);

  • Twitter
  • Facebook
  • Google Plus
  • LinkedIn
  • Pinterest
  • StumbleUpon
  • Technorati
  • Delicious
  • Digg
  • Email
  • Print

How to remove old and hidden device drivers from windows

Here’s a quick rundown on how to get rid of unused / old / hidden device drivers in windows (on Windows 7, but should work pretty much on any other version) – RPN5VQ7EECJQ.

Anytime you add a device and windows asks you for a driver, or looks on the internet and finds the driver for you, once installed, chances are it will stay around for good. And what happens at times is that when you connect some other device, the wrong driver gets picked up automatically among the ones you have already installed.

Typical scenario? You connect an android phone or tablet via usb to your pc, the device has “usb debugging” enabled, but despite what you try out, “adb devices” won’t show. Chances are the wrong adb interface driver is being used for your device.

So here’s how to get rid of unused drivers (i.e. devices not shown when disconnected):

- Add the environment variable devmgr_show_nonpresent_devices to your user or system variables, and set its value to 1 (command prompt -> control.exe sysdm.cpl,System,3 then press “Environment Variables” to get to the dialog where to add what above).

- Launch the device manager (command prompt ->  devmgmt.msc) then menu -> view -> show hidden devices. At that point you’ll be able to see any previously connected device, right click on it, and select “uninstall”. In the dialog that appears make sure to check “delete the driver software for this device”.

  • Twitter
  • Facebook
  • Google Plus
  • LinkedIn
  • Pinterest
  • StumbleUpon
  • Technorati
  • Delicious
  • Digg
  • Email
  • Print

How to build the latest node.js RPM and install it on CentOS / RedHat / Fedora

Building nodejs RPMs on CentOS

If you aren't familiar with node.js, it's a platform whose goal is to facilitate building event-driven server side javascript services. Essentially it allows to run javascript on the server -- services built with Node.js go to sleep after instructing … [Continue reading]