General Thankyou (still diagnosing fault)

Dave Filchak dave.filchak at senecac.on.ca
Sun Jan 11 21:17:56 GMT 2009


Jules,

Julian Field wrote:
>
>
> On 11/1/09 20:16, Dave Filchak wrote:
>> Jules
>>
>> Julian Field wrote:
>>>
>>>
>>> On 11/1/09 19:03, Dave Filchak wrote:
>>>> Kai,
>>>>
>>>>
>>>>
>>>> Dave Filchak wrote:
>>>>> Kai,
>>>>>
>>>>> Kai Schaetzl wrote:
>>>>>> Dave Filchak wrote on Fri, 09 Jan 2009 14:06:02 -0500:
>>>>>>
>>>>>>
>>>>>>> So I checked the permissions there and the Locks directory is 
>>>>>>> owned by postfix.root and the locks inside are all owned by 
>>>>>>> root.root.
>>>>>>
>>>>>> That is *all* wrong. Reread the tutorials for MS+postfix and for 
>>>>>> MS+clamd (you are using clamd, right).
>>>>>>
>>>>>> /var/spool/MailScanner/incoming/Locks l
>>>>>> total 16
>>>>>> drwxr-x--- 2 root    postfix 4096 Jan  9 23:03 .
>>>>>> drwxr-xr-x 5 postfix clamav  4096 Jan  9 23:04 ..
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 antivirBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 avastBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 avgBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 bitdefenderBusy.lock
>>>>>> -rw------- 1 postfix postfix  100 Jan  9 23:05 clamavBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 cssBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 esetsBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 etrustBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 f-prot-6Busy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 f-protBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 f-secureBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 genericBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 inoculanBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 kasperskyBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 mcafeeBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Jan  7 16:51 MS.bayes.rebuild.lock
>>>>>> -rw------- 1 postfix postfix    0 Jan  9 23:03 
>>>>>> MS.bayes.starting.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 nod32Busy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 normanBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 pandaBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 ravBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 sophosBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 
>>>>>> symscanengineBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 trendBusy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 vba32Busy.lock
>>>>>> -rw------- 1 postfix postfix    0 Dec 11 17:31 vexiraBusy.lock
>>>>>>
>>>>>> Kai
>>>>>>
>>>>> Well I will definitely reread these. I never specifically set 
>>>>> these permissions anywhere. One would thing that these would be 
>>>>> created by the settings in MailScanner.conf .. wouldn't you? There 
>>>>> is no specific alternate user settings in spamassassin so  .... 
>>>>> something is setting these permissions this way.
>>>>>
>>>> I have gone through the tutorials a few times and I seem to have 
>>>> everything set up correctly yet .... something keeps reseting the 
>>>> permissions in the Locks directory back to the following:
>>> It will be being clobbered by the update_virus_scanners cron job 
>>> which is run once per hour. Please can you mail me an exact copy 
>>> (preferably gzipped) of your MailScanner.conf file. Have you moved 
>>> that file from its default location or anything like that? It should 
>>> pull out the "Run As User" and "Run As Group" from MailScanner.conf 
>>> and use those values to set the ownership of the lock files. Clearly 
>>> something is going wrong there.
>>>
>>> Copy and paste the following commands into a shell running as root. 
>>> Beware of extra line-breaks that my mail program or your mail 
>>> program may add into the following, hopefully they'll be okay.
>>>
>>> LOCKDIR=`perl -n -e 'print "$_" if chomp && 
>>> s/^\s*Lock\s*file\s*Dir\s*=\s*(\S+)/$1/i' 
>>> /etc/MailScanner/MailScanner.conf`
>>> RUNASU=`perl -n -e 'print "$_" if chomp && 
>>> s/^\s*Run\s*As\s*User\s*=\s*(\S+)/$1/i' 
>>> /etc/MailScanner/MailScanner.conf`
>>> RUNASG=`perl -n -e 'print "$_" if chomp && 
>>> s/^\s*Run\s*As\s*Group\s*=\s*(\S+)/$1/i' 
>>> /etc/MailScanner/MailScanner.conf`
>>> echo $LOCKDIR
>>> echo $RUNASU
>>> echo $RUNASG
>>> /usr/sbin/mailscanner_create_locks "$LOCKDIR" "$RUNASU" "$RUNASG"
>>>
>>> Then show me what you get from
>>>     ls -al $LOCKDIR
>>> assuming that the "echo $LOCKDIR" command printed out the directory 
>>> where your lock files are stored (i.e. normally 
>>> /var/spool/MailScanner/incoming/Locks).
>>
>> I have emailed you my conf file. Here is the output from your scripts:
>>
>> [root at rosewood MailScanner]# LOCKDIR=`perl -n -e 'print "$_" if chomp 
>> && s/^\s*Lock\s*file\s*Dir\s*=\s*(\S+)/$1/i' 
>> /etc/MailScanner/MailScanner.conf`
>> [root at rosewood MailScanner]# RUNASU=`perl -n -e 'print "$_" if chomp 
>> && s/^\s*Run\s*As\s*User\s*=\s*(\S+)/$1/i' 
>> /etc/MailScanner/MailScanner.conf`
>> [root at rosewood MailScanner]# RUNASG=`perl -n -e 'print "$_" if chomp 
>> && s/^\s*Run\s*As\s*Group\s*=\s*(\S+)/$1/i' 
>> /etc/MailScanner/MailScanner.conf`
>> [root at rosewood MailScanner]# echo $LOCKDIR
>> /var/spool/MailScanner/incoming/Locks
>> [root at rosewood MailScanner]# echo $RUNASU
>> postfix
>> [root at rosewood MailScanner]# echo $RUNASG
>> postfix
> That all looks good. As root,
>     rm -rf /var/spool/MailScanner/incoming/Locks
> and then
>     /usr/sbin/update_virus_scanners
> and then show me an
>     ls -al /var/spool/MailScanner/incoming/Locks
>
> The files in there should be owned by postfix. Let's see if that's true.
>
OK .. deleted the Locks directory, ran update_virus_scanners and got:

ls -al /var/spool/MailScanner/incoming/Locks/
total 8
drwxr-x---  2 root    root   4096 Jan 11 16:13 .
drwxrwx---  7 postfix clamav 4096 Jan 11 16:14 ..
-rw-------  1 root    root      0 Jan 11 16:13 antivirBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 avastBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 avgBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 bitdefenderBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 clamavBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 cssBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 esetsBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 etrustBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 f-prot-6Busy.lock
-rw-------  1 root    root      0 Jan 11 16:13 f-protBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 f-secureBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 genericBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 inoculanBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 kasperskyBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 mcafeeBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 MS.bayes.rebuild.lock
-rw-------  1 root    root      0 Jan 11 16:13 MS.bayes.starting.lock
-rw-------  1 root    root      0 Jan 11 16:13 nod32Busy.lock
-rw-------  1 root    root      0 Jan 11 16:13 normanBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 pandaBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 ravBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 sophosBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 symscanengineBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 trendBusy.lock
-rw-------  1 root    root      0 Jan 11 16:13 vba32Busy.lock
-rw-------  1 root    root      0 Jan 11 16:13 vexiraBusy.lock


Still root.

Dave
>>
>> Dave
>>>
>>>>
>>>> -rw-------  1 root root  0 Jan  8 05:09 antivirBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 avastBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 avgBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 bitdefenderBusy.lock
>>>> -rw-------  1 root root 49 Jan  9 19:15 clamavBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 cssBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 esetsBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 etrustBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 f-prot-6Busy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 f-protBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 f-secureBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 genericBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 inoculanBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 kasperskyBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 mcafeeBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 19:38 MS.bayes.rebuild.lock
>>>> -rw-------  1 root root  0 Jan 11 04:15 MS.bayes.starting.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 nod32Busy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 normanBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 pandaBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 ravBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 sophosBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 symscanengineBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 trendBusy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 vba32Busy.lock
>>>> -rw-------  1 root root  0 Jan  8 05:09 vexiraBusy.lock
>>>>
>>>> /var/spool/MailScanner/incoming
>>>> [root at rosewood incoming]# ls -l
>>>> total 604
>>>> drwxr-x---  2 postfix clamav    4096 Jan 11 13:43 19962
>>>> drwxr-x---  2 postfix clamav    4096 Jan 11 13:38 19969
>>>> drwxr-x---  2 postfix clamav    4096 Jan 11 13:41 19976
>>>> drwxr-x---  2 postfix root      4096 Jan 11 04:15 Locks
>>>> -rw-------  1 postfix postfix 590848 Jan 11 13:41 
>>>> SpamAssassin.cache.db
>>>> drwx------  2 postfix postfix   4096 Jan 11 13:43 SpamAssassin-Temp
>>>>
>>>> Yesterday this was all set as you have it above.
>>>>
>>>> Dave
>>>
>>> Jules
>>>
>>
>
> Jules
>

-- 
Dave Filchak
Instructor, School of Communications Arts
Seneca College @ York
Office: Room 1068



More information about the MailScanner mailing list