Hi Jenny,
On Wed, Jun 25, 2003 at 04:25:08PM -0600, Jenny Fox wrote:
> I have a mostly successful installation of otrs on a system running
> Solaris 8. The problem is when I try to run the Postmaster.pl script I
> get the following error:
>
> > cat test-message | bin/PostMaster.pl
> unix passed to setlogsock, but path not available at
> /opt/local/apache/htdocs/otrs/Kernel/System/Log/SysLog.pm line 39
>
> I did some research on the web and found the following:
> >The Sys::Syslog module breaks rather badly on Solaris in a
> >couple of cases:
> >
> >1) there's no support for the setlogsock('unix') used in
> >MIMEDefang. Solaris has no unix socket for syslog at all.
> >
> >2) if you run syslogd with the -t flag, to make it not listen
> >on its udp socket (pretty standard on secure boxes), then the
> >Sys::Syslog module won't log anything! It won't error, but it
> >won't log, either.
> >
> >One solution is to use the Unix::Syslog CPAN module, which wraps
> >the OS's native C syslog calls to log directly to syslog. This
> >works great for me on my secured Solaris boxes.
>
> We do, in fact, run syslogd with the -t option, so I couldn't use the
> setlogsock('inet') option, and I tried using the Unix::Syslog module
> but it apparently doesn't have a setlogsock routine?
>
> Does anyone have any suggestions?
How about to use the file-log backend? So you don't need to log with
syslog.
Add the following to Kernel/Config.pm
[...]
$Self->{LogModule} = 'Kernel::System::Log::File';
$Self->{'LogModule::LogFile'} = '/tmp/otrs.log';
[...]
I hope this helps you! :)
> --jenny
>
> Jennifer Fox
> Unix System Administrator
> NOAA Aeronomy Laboratory, Boulder, CO
-Martin
--
Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/
--
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
