Hi,
Just upgraded from 3.6.6 to 3.8.2 running on Solaris 10. Now I find
myself struggling to the the syslog stuff to work.
Here are the settings that I had thought would work from my
understanding of the docs
and googling:
Set(@LogToSyslogConf = ( socket => ‘stream’));
[Sat Feb 14 11:18:58 2009] [error] [client 169.229.201.201] undef is not
a valid Log::Dispatch log level at /opt/rt3/bin/…/lib/RT.pm line 341\n
Does anyone have rt 3.8.2 working on Solaris 10? Care to share your
LogToSyslogConf settings?
Hi,
Just upgraded from 3.6.6 to 3.8.2 running on Solaris 10. Now I find
myself struggling to the the syslog stuff to work.
Here are the settings that I had thought would work from my
understanding of the docs
and googling:
What have you set $LogToSyslog to (that seems to be the source of the
undef error you’re seeing)
In addition, I know that on Solaris 8 and 9 I needed ( socket =>
‘inet’ )
to avoid problems (which is what is documented in RT_Config.pm),
but I haven’t had a chance to play with Solaris 10 yet.
-kevin
Kevin Falcone wrote:> On Feb 14, 2009, at 2:23 PM, Gary Casterline wrote:
Hi,
Just upgraded from 3.6.6 to 3.8.2 running on Solaris 10. Now I find
myself struggling to the the syslog stuff to work.
Here are the settings that I had thought would work from my
understanding of the docs
and googling:
What have you set $LogToSyslog to (that seems to be the source of the
undef error you’re seeing)
In addition, I know that on Solaris 8 and 9 I needed ( socket =>
‘inet’ )
to avoid problems (which is what is documented in RT_Config.pm),
but I haven’t had a chance to play with Solaris 10 yet.
-kevin
Just tried it again with
Set($LogToSyslog , ‘debug’);
Set(@LogToSyslogConf = ( socket => ‘inet’));
and still get
[Sun Feb 15 13:20:53 2009] [error] [client 169.229.201.201] undef is not
a valid Log::Dispatch log level at /opt/rt3/bin/…/lib/RT.pm line 341\n
After making a change to RT_SiteConfig.pm, is it necessary to restart
apache or anything?
Yes, any time you make a change to RT_SiteConfig.pm, it’s necessary to
restart apache and clear out the mason cache. Reference the readme docs.
James Moseley
Gary Casterline
<casterln@nature.
berkeley.edu> To
Sent by: RT Users
rt-users-bounces@ <RT-Users@lists.bestpractical.com>
lists.bestpractic cc
al.com
Subject
Re: [rt-users] solaris 10 syslog
02/15/2009 03:23 woes
PM
After making a change to RT_SiteConfig.pm, is it necessary to restart
apache or anything?
Yes, any time you make a change to RT_SiteConfig.pm, it’s necessary to
restart apache and clear out the mason cache.
Actually, for changes to lib and etc, you need only stop and start
apache. The mason cache is only for templates.
Thanks. Good to know Jesse.
James Moseley
Jesse Vincent
<jesse@bestpracti
cal.com> To
02/15/2009 03:54 jmoseley@corp.xanadoo.com
PM cc
Gary Casterline
<casterln@nature.berkeley.edu>, RT
Users
<RT-Users@lists.bestpractical.com>,
rt-users-bounces@lists.bestpractica
l.com
Subject
Re: [rt-users] solaris 10 syslog
woes
Actually, for changes to lib and etc, you need only stop and start
apache. The mason cache is only for templates.