error from Klamav
Thanks for your help, Scott.
On 30/08/11 11:14, Scott Ferguson wrote: On 30/08/11 19:18, Tony van der Hoff wrote: On 30/08/11 10:03, Scott Ferguson wrote: On 30/08/11 18:09, Tony van der Hoff wrote: I am getting an error after the nightly scan by KlamAV as follows: From: root@tony-lx.xxx (Cron Daemon) To: tony@tony-lx.xxx Subject: Cron <tony@tony-lx> /home/tony/.klamav/ScanWithKlamav_170811104108.sh '/home/tony/' [...] Which Debian release are you running?? Squeeze That script "used" to be for KDE context menu a long time ago. cat: /home//.DCOPserver_tony-lx_:0: No such file or directory call failed QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout Does anyone have any clues to what this means, and more importantly, how to fix it? Thanks in advance, Has the process previously worked successfully?? No. I recently installed it with synaptic, configured it to scan my home, and left it at that. It seems to be looking for .DCOPserver_tony-lx_:0 in /home, whereas that file actually exists in /home/tony. I had no problem manually scanning a home directoy using Klamav - when I used Klamav to setup a scheduled scan it created:- ~/.klamav/ScanWithKlamav_timestring.sh After looking (quickly) at that script I suspect (strongly) that the ${USER} is probably not being populated. You could try replacing it with the hardcoded value eg:- line 6 would become:- DCOPSERVER=`cat /home/tony/.DCOPserver_${HOSTNAME}_:) | grep local` In fact I suggest replace the HOSTNAME variable as well as your error string doesn't contain either the $USER or the $HOSTNAME (the script populates $HOSTNAME with 'hostname' which doesn't seem helpful. If that solves the problem please file a bug report. - Doing a manual scan works fine, as you found. - My crontab was appended (presumably by the installer) with: # KlamAV Scheduled Scan of /home/tony/ 0 6 * * * /home/tony/.klamav/ScanWithKlamav_170811104108.sh '/home/tony/' # This file was written by KlamAV using code disembowelled from KCron. # KCron is (c) 1999, Gary Meyer; if your cron file looks screwed up # then that is probably (c) Robert Hogan and you should file a bug report. # Original notice from KCron reads: # Although KCron supports most crontab formats, use care when editing. # Note: Lines beginning with "#" indicates a disabled task. - My $USER is set in my login environment, but presumably not in the cron environment: tony@tony-lx:~$ echo $USER tony - The Hostname (tony-lx) is actually recognised by the script. In fact it is set within the script: HOSTNAME=`hostname` export HOSTNAME So, it is the lack of $USER that is the problem, as you correctly observe. I'm not sure whether this should be set by cron; I suspect not. From man 5 crontab: ---- Several environment variables are set up automatically by the cron(8) daemon. SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd line of the crontab's owner. PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be overridden by settings in the crontab; LOGNAME is the user that the job is running from, and may not be changed. (Another note: the LOGNAME variable is sometimes called USER on BSD systems... on these systems, USER will be set also.) ---- Therefore it appears that (on Linux at least) the KlamAV script should be using $LOGNAME rather than $USER. I'll amend that, and report back tomorrow, after the next cron run at 0600. If it succeeds, and no-one here has alternative suggestions, I'll raise a bug. Cheers, -- Tony van der Hoff | mailto:tony@vanderhoff.org Buckinghamshire, England | -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4E5CCC87.7030309@vanderhoff.org">http://lists.debian.org/4E5CCC87.7030309@vanderhoff.org |
error from Klamav
On 30/08/11 21:41, Tony van der Hoff wrote:
Thanks for your help, Scott. On 30/08/11 11:14, Scott Ferguson wrote: On 30/08/11 19:18, Tony van der Hoff wrote: On 30/08/11 10:03, Scott Ferguson wrote: On 30/08/11 18:09, Tony van der Hoff wrote: I am getting an error after the nightly scan by KlamAV as follows: From: root@tony-lx.xxx (Cron Daemon) To: tony@tony-lx.xxx Subject: Cron <tony@tony-lx> /home/tony/.klamav/ScanWithKlamav_170811104108.sh '/home/tony/' [...] <snipped> If it succeeds, and no-one here has alternative suggestions, I'll raise a bug. Cheers, I don't personally use it, and my systems are too heavily modified to be useful for bug reports, so I won't file one. I install klamav for the benefit of, um, operators - but I enforce scans using clamav cron jobs (the gui seems redundant for those). At some stage I should file a bug report for the minor problem Klamav has when you close - it puts out a useless error message about updates being killed - when nothing of the sort actually happens. Cheers -- "Folks, it's time to evolve. That's why we're troubled. You know why our institutions are failing us, the church, the state, everything's failing? It's because, um – they're no longer relevant. We're supposed to keep evolving. Evolution did not end with us growing opposable thumbs. You do know that, right? There's another 90 percent of our brains that we have to illuminate." — Bill Hicks -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4E5CD4CE.1070108@gmail.com">http://lists.debian.org/4E5CD4CE.1070108@gmail.com |
error from Klamav
On 30/08/11 12:41, Tony van der Hoff wrote:
Thanks for your help, Scott. On 30/08/11 11:14, Scott Ferguson wrote: On 30/08/11 19:18, Tony van der Hoff wrote: On 30/08/11 10:03, Scott Ferguson wrote: On 30/08/11 18:09, Tony van der Hoff wrote: I am getting an error after the nightly scan by KlamAV as follows: From: root@tony-lx.xxx (Cron Daemon) To: tony@tony-lx.xxx Subject: Cron <tony@tony-lx> /home/tony/.klamav/ScanWithKlamav_170811104108.sh '/home/tony/' [...] cat: /home//.DCOPserver_tony-lx_:0: No such file or directory call failed QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout Does anyone have any clues to what this means, and more importantly, how to fix it? [snips] Therefore it appears that (on Linux at least) the KlamAV script should be using $LOGNAME rather than $USER. I'll amend that, and report back tomorrow, after the next cron run at 0600. If it succeeds, and no-one here has alternative suggestions, I'll raise a bug. Well, that partially solved the problem. It got rid of "no such file or directory" error, but I am still left with call failed QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout Now I'm stuck for an idea... -- Tony van der Hoff | mailto:tony@vanderhoff.org Buckinghamshire, England | -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4E5DE61B.9020500@vanderhoff.org">http://lists.debian.org/4E5DE61B.9020500@vanderhoff.org |
error from Klamav
On 31/08/11 17:43, Tony van der Hoff wrote:
On 30/08/11 12:41, Tony van der Hoff wrote: Thanks for your help, Scott. On 30/08/11 11:14, Scott Ferguson wrote: On 30/08/11 19:18, Tony van der Hoff wrote: On 30/08/11 10:03, Scott Ferguson wrote: On 30/08/11 18:09, Tony van der Hoff wrote: I am getting an error after the nightly scan by KlamAV as follows: From: root@tony-lx.xxx (Cron Daemon) To: tony@tony-lx.xxx Subject: Cron <tony@tony-lx> /home/tony/.klamav/ScanWithKlamav_170811104108.sh '/home/tony/' [...] cat: /home//.DCOPserver_tony-lx_:0: No such file or directory call failed QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout Does anyone have any clues to what this means, and more importantly, how to fix it? [snips] Therefore it appears that (on Linux at least) the KlamAV script should be using $LOGNAME rather than $USER. I'll amend that, and report back tomorrow, after the next cron run at 0600. If it succeeds, and no-one here has alternative suggestions, I'll raise a bug. Well, that partially solved the problem. It got rid of "no such file or directory" error, but I am still left with call failed QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout Now I'm stuck for an idea... Sorry that didn't solve all the problems - I'll have another look at the script later this evening - I only had a quick glance last night. Did it do a scan? If not:- Does update work OK? (/var/log/klamav/freshclam.log) If update (freshclam) hasn't been working then a scan won't either:- # chmod 777 /var/lib/klamav also make sure you a member of clamav:- $ groups | grep clamav Cheers -- "The definition of black irony is Pro-lifers killing Doctors who do abortions" — Bill Hicks -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4E5DFF00.6090605@gmail.com">http://lists.debian.org/4E5DFF00.6090605@gmail.com |
error from Klamav
On 31/08/11 10:29, Scott Ferguson wrote:
On 31/08/11 17:43, Tony van der Hoff wrote: On 30/08/11 12:41, Tony van der Hoff wrote: Thanks for your help, Scott. On 30/08/11 11:14, Scott Ferguson wrote: On 30/08/11 19:18, Tony van der Hoff wrote: On 30/08/11 10:03, Scott Ferguson wrote: On 30/08/11 18:09, Tony van der Hoff wrote: I am getting an error after the nightly scan by KlamAV as follows: From: root@tony-lx.xxx (Cron Daemon) To: tony@tony-lx.xxx Subject: Cron <tony@tony-lx> /home/tony/.klamav/ScanWithKlamav_170811104108.sh '/home/tony/' [...] cat: /home//.DCOPserver_tony-lx_:0: No such file or directory call failed QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout Does anyone have any clues to what this means, and more importantly, how to fix it? [snips] Therefore it appears that (on Linux at least) the KlamAV script should be using $LOGNAME rather than $USER. I'll amend that, and report back tomorrow, after the next cron run at 0600. If it succeeds, and no-one here has alternative suggestions, I'll raise a bug. Well, that partially solved the problem. It got rid of "no such file or directory" error, but I am still left with call failed QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout Now I'm stuck for an idea... Sorry that didn't solve all the problems - I'll have another look at the script later this evening - I only had a quick glance last night. Did it do a scan? If not:- Does update work OK? (/var/log/klamav/freshclam.log) If update (freshclam) hasn't been working then a scan won't either:- # chmod 777 /var/lib/klamav also make sure you a member of clamav:- $ groups | grep clamav Yeah, it seems to work OK, always did; even found some MyDoom, and quarantined it, so I'm not too worried. Thanks for looking. Cheers, -- Tony van der Hoff | mailto:tony@vanderhoff.org Buckinghamshire, England | -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4E5E012F.4080001@vanderhoff.org">http://lists.debian.org/4E5E012F.4080001@vanderhoff.org |
error from Klamav
On 31/08/11 19:38, Tony van der Hoff wrote:
On 31/08/11 10:29, Scott Ferguson wrote: On 31/08/11 17:43, Tony van der Hoff wrote: On 30/08/11 12:41, Tony van der Hoff wrote: Thanks for your help, Scott. On 30/08/11 11:14, Scott Ferguson wrote: On 30/08/11 19:18, Tony van der Hoff wrote: On 30/08/11 10:03, Scott Ferguson wrote: On 30/08/11 18:09, Tony van der Hoff wrote: I am getting an error after the nightly scan by KlamAV as follows: <snipped> Yeah, it seems to work OK, always did; even found some MyDoom, and quarantined it, so I'm not too worried. Thanks for looking. Cheers, Glad it's working for you. The "QLayout "unnamed" added to Klamav "KlamAV "" message is just another broken/undocumented feature in Klamav - nothing to do with a cron job. I thought dcop was deprecated in KDE4, so how come dbus isn't being used? hmmm :-/ It lead to me reading the clamav documentation and discovering clampipe. So I now have something else to add to my to-do-when-I-get-time list - enable clamav scanning of Icedove emails! Then I'll be able to add an email signature "this email has been scanned with ClamAV". It will make recipients feel much safer (which is good, right?) :-D Cheers -- "The definition of black irony is Pro-lifers killing Doctors who do abortions" — Bill Hicks -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4E5E1834.203@gmail.com">http://lists.debian.org/4E5E1834.203@gmail.com |
error from Klamav
On 31/08/11 12:17, Scott Ferguson wrote:
On 31/08/11 19:38, Tony van der Hoff wrote: On 31/08/11 10:29, Scott Ferguson wrote: On 31/08/11 17:43, Tony van der Hoff wrote: On 30/08/11 12:41, Tony van der Hoff wrote: Thanks for your help, Scott. On 30/08/11 11:14, Scott Ferguson wrote: On 30/08/11 19:18, Tony van der Hoff wrote: On 30/08/11 10:03, Scott Ferguson wrote: On 30/08/11 18:09, Tony van der Hoff wrote: I am getting an error after the nightly scan by KlamAV as follows: <snipped> Yeah, it seems to work OK, always did; even found some MyDoom, and quarantined it, so I'm not too worried. Thanks for looking. Cheers, Glad it's working for you. The "QLayout "unnamed" added to Klamav "KlamAV "" message is just another broken/undocumented feature in Klamav - nothing to do with a cron job. I'm thinking that KlamAV really doesn't deserve to be in Debian Stable! About time to abandon it! I thought dcop was deprecated in KDE4, so how come dbus isn't being used? hmmm :-/ It lead to me reading the clamav documentation and discovering clampipe. So I now have something else to add to my to-do-when-I-get-time list - enable clamav scanning of Icedove emails! Then I'll be able to add an email signature "this email has been scanned with ClamAV". It will make recipients feel much safer (which is good, right?) :-D I've always felt messages like that to be the extreme in irony. If I wanted to add malware to a mail, I'd also add such a message, just to make it more attractive! -- Tony van der Hoff | mailto:tony@vanderhoff.org Buckinghamshire, England | -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4E5E24E3.4040505@vanderhoff.org">http://lists.debian.org/4E5E24E3.4040505@vanderhoff.org |
| All times are GMT. The time now is 03:40 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.