$LogDir in RT 3-0-2

This message was transferred with a trial version of CommuniGate™ Pro
Hello,

I’m new to RT (haven’t used version 2) and have started to get things
working. I noticed errors in apache’s error_log file that have helped me
configure a few things correctly and also wondered if I would see any
messages in RT’s own log.

I have an /opt/rt3/var/log directory but no logs in this.

I the have settings in RT_SiteConfig.pm:

Set($LogToSyslog , ‘debug’);
Set($LogToScreen , ‘error’);
Set($LogToFile , undef);
Set($LogToFileNamed , “$LogDir/rt.log”); #log to rt.log..

I assume I need to change $logToFile from undef to something like ‘info’ to
get messages of info level and above?

I notice from looking at email archives that version 2 config.pm has $LogDir
defined further up in the file, but is not in the default configuration for
version 3. Do I need to add something like Set($LogDir , “/opt/rt3/var/log”)
to the config.pm, depending on where I would like the log files to go?

Regards,

Jim

This message was transferred with a trial version of CommuniGate™ Pro
Found out some more on this and thought I’d try to answer my own post,
please enlighten me if I’m incorrect.

I the have settings in RT_SiteConfig.pm:

Set($LogToSyslog , ‘debug’);
Set($LogToScreen , ‘error’);
Set($LogToFile , undef);
Set($LogToFileNamed , “$LogDir/rt.log”); #log to rt.log..

I assume I need to change $logToFile from undef to something like 'info’
to
get messages of info level and above?

Have done the above and changed ownership of /opt/rt3/var/log so that apache
can write to it (without this RT won’t work as it cannot write logs).
Getting some useful info in the logs now.

I notice from looking at email archives that version 2 config.pm has
$LogDir
defined further up in the file, but is not in the default configuration
for
version 3. Do I need to add something like Set($LogDir ,
"/opt/rt3/var/log")
to the config.pm, depending on where I would like the log files to go?

In the /lib/RT.pm $LogDir is set. I guess I could alter it
there if necessary but it would seem neater to change this in
RT_SiteConfig.pm.

A humble suggestion:

I don’t know if this is something that can be added to the installation
process of version 3, but it would be useful to have logging working by
default. Could the appropriate configuration settings be put in RT_Config.pm
and permissions set on the default log directory as they seem to be on
mason_data and session_data in the log directory? Would help the initial
configuration process and the newbie greatly.

Regards,

Jim

In the /lib/RT.pm $LogDir is set. I guess I could alter it
there if necessary but it would seem neater to change this in
RT_SiteConfig.pm.

This has been fixed in the repository and will appear in 3.0.3

A humble suggestion:

I don’t know if this is something that can be added to the installation
process of version 3, but it would be useful to have logging working by
default. Could the appropriate configuration settings be put in RT_Config.pm
and permissions set on the default log directory as they seem to be on
mason_data and session_data in the log directory? Would help the initial
configuration process and the newbie greatly.

By default, RT 3.0 logs to the syslog, which requires even less
configuration.

Regards,

Jim


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

This message was transferred with a trial version of CommuniGate™ Pro
Jesse,

In the /lib/RT.pm $LogDir is set. I guess I could alter
it

there if necessary but it would seem neater to change this in
RT_SiteConfig.pm.

This has been fixed in the repository and will appear in 3.0.3

Thanks :slight_smile:

A humble suggestion:

I don’t know if this is something that can be added to the installation
process of version 3, but it would be useful to have logging working by
default. Could the appropriate configuration settings be put in
RT_Config.pm

and permissions set on the default log directory as they seem to be on
mason_data and session_data in the log directory? Would help the initial
configuration process and the newbie greatly.

By default, RT 3.0 logs to the syslog, which requires even less
configuration.

Again thanks, that seems a better way to go. This may explain the message
below (in apache’s error_log) following the installation. I have yet to try
to resolv this one, but assumed I was having a perl problem rather than
something specific to RT.

[Mon May 19 11:51:08 2003] Syslog.pm: unix passed to setlogsock, but path
not available at /usr/local/lib/perl5/site_perl/5.8.0
/Log/Dispatch/Syslog.pm line 66

Regards,

Jim

Jim Mozley wrote:

[Mon May 19 11:51:08 2003] Syslog.pm: unix passed to setlogsock, but path
not available at /usr/local/lib/perl5/site_perl/5.8.0
/Log/Dispatch/Syslog.pm line 66

You’re using Solaris (or maybe HP/UX), right?

Sys::Syslog does not like Solaris, where /dev/log is not a socket.
Grab a copy of the Sys::Syslog sources and look for “Solaris” in
the Makefile.PL. You can probably fudge the $_PATH_LOG setting in
that file to be /dev/log and live with the broken “make test”, or
you could work out a proper solution and submit it to the author.
:wink:
�|� http://www.bestpractical.com/rt – Trouble Ticketing. Free.