logging problem

[Richard Hopkins]

For us, SpamAssassin stopped logging when syslogd was restarted with a "-t"
(Solaris 2.8 systems).

Richard

--On Thursday, June 12, 2003 8:30 AM -0500 David Vosburgh
<vosburgh at DALSEMI.COM> wrote:

> I have, but there is no "-T" option to syslogd for Solaris (at least
> from 2.6 through 2.8).  There is a "-t" option (disable the syslogd UPD
> port), which is the default, and the way syslogd was running when I
> first started MailScanner.  When that didn't work, I read the FAQ, which
> suggested removing it.  I did, but it didn't fix the logging problem.
>
> Dave
>
> Julian Field wrote:
>
>> Have you read the syslogd man page and added the "-T" option to the
>> syslogd
>> command in /etc/init.d/syslog. I seem to remember you usually need to
>> turn
>> this on.
>>
>> At 12:32 12/06/2003, you wrote:
>>
>>> I get the normal sendmail logs to maillog, but nothing from
>>> mailscanner/spamassassin.
>>>
>>> I did some testing with Sys::Syslog and I think that's where the problem
>>> is.  Even extremely simple attempts to log a message failed (without
>>> errors).  A quick look on SunSolve didn't reveal any known compatibility
>>> issues with syslogd, although there was a very current patch for syslog
>>> out there.  Because we need to get the spam logging working to collect
>>> metrics prior to a production roll-out, I brute forced it by changing a
>>> few of the Sys:Syslog calls in Log.pm to use system calls to logger
>>> instead.
>>>
>>> Dave
>>>
>>> Peter Bonivart wrote:
>>>
>>>> Strange, I have a similar setup (Solaris 9, Sendmail 8.12.9,
>>>> MailScanner
>>>> 4.21-6 and SpamAssassin 2.54). The only thing I changed in
>>>> MailScanner.conf regarding this was "Log Spam = yes". Nothing is
>>>> changed
>>>> in the system and everything is logged.
>>>>
>>>> Do you get any logs at all from sendmail/mailscanner/spamassassin?
>>>>
>>>> /Peter Bonivart
>>>>
>>>> --Unix lovers do it in the Sun
>>>>
>>>> On Mon, 2003-06-09 at 21:54, David Vosburgh wrote:
>>>>
>>>>
>>>>> I have installed MailScanner-4.21-9, Mail-SpamAssassin-2.55, and
>>>>> all the
>>>>> related perl modules on a Sun system recently jumpstarted with 2.8
>>>>> and a
>>>>> recent patch cluster.  Sendmail is v8.12.9.
>>>>>
>>>>> Everything seems to be working as advertised, with the exception of
>>>>> logging.  I am using the default "Syslog Facility = mail" option, and
>>>>> have turned on spam logging with "Log Spam = yes". My syslog.conf
>>>>> has a
>>>>> single entry for mail logging:
>>>>>
>>>>> mail.info                                       /var/adm/maillog
>>>>>
>>>>> I read the FAQ and some posts on this list, and have tried the
>>>>> following
>>>>> without success (always re-starting MailScanner after the change):
>>>>>
>>>>> 1) starting syslog without the "-t" option
>>>>> 2) removed the syslog patch 110945-07 (now -05)
>>>>> 3) removed the "eval" from the setlogsock syslog command under the
>>>>> Start
>>>>> section of Log.pm
>>>>> 4) added a "mail.debug /opt/MailScanner/var/log" to syslog.conf
>>>>>
>>>>> Any ideas on where to go from here?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Dave
>>>>>
>>>>
>>>>
>>>
>>> --
>>>
>>> Dave Vosburgh
>>> Sr. Unix System Administrator
>>> Dallas Semiconductor
>>> vosburgh at dalsemi.com  972-371-4418
>>
>>
>> --
>> Julian Field
>> www.MailScanner.info
>> MailScanner thanks transtec Computers for their support
>>
>
> --
>
> Dave Vosburgh
> Sr. Unix System Administrator
> Dallas Semiconductor
> vosburgh at dalsemi.com  972-371-4418
>



Richard Hopkins,
Information Services,
Computer Centre,
University of Bristol,
Bristol, BS8 1UD, UK

Tel +44 117 928 7859
Fax +44 117 929 1576