Thanks for the info. Could be useful but I'll try to stay away from the
Event Log (explained why in another reply in this thread).
In case anyone anyone stumbles upon this thread in the future: I tested and
otrs.log can be rotated manually. OTRS doesn't hold a permanent lock and so
an external too
The only problem is to use a logging framework that is advanced enough to make
it easy for admins when deciding what goes into the file and how size is
managed. Look at log4j as a model. I see there's a version for Perl also (
http://mschilli.github.com/log4perl/ ). If it's good enough and it ha
I recommend you ignore Windows Event Log and use a logging framework that
handles file logging at the same capability level as log4j. Reasons are
below.
Most applications writing to Windows' Event Log do so in a non-chatty
manner, for special events. You will at least have to comply with this
modu
Hi all,
Usually, when a cronjob fails, it sends a mail to user@hostname.
Some weeks ago, I was testing a Generic Agent task in DEV environment and it
failed. The job was running as OTRS user, so the mail went to otrs@hostname and
it went into the system in the first otrs.PostMasterMailbox.pl e
In newer releases of the OTRS Windows installer I made sure Sys::Syslog is
installed, so you can use it if you want. Also I'd like to switch to using the
Windows event log by default in the 'future', meaning probably for OTRS 3.3.
Great news. There’s no excuse these days for inventing your own l
It's a core module of perl (and in 'corelist') but beware: it is not
installed by default if you're on Windows.
You can add it afterwards using cpan, but not if your perl is in a path
containing spaces (such as when you installed using the OTRS installer in
C:\Program Files\OTRS)
In newer releases
You don't have to use LogFile. You can use SysLog and handle that way
Second this suggestion. Individual log files for applications are a bloody
nightmare (particularly if any automation or monitoring is done) and should be
stamped out wherever possible.
Sys::Syslog is a core module of perl. Changing the method to Syslog
$Self->{LogModule} = 'Kernel::System::Log::SysLog';
$Self->{'LogModule::SysLog::LogSock'} = 'eventlog';
Theoretically, you should be able to see if this works quite quickly.
On Tue, Mar 26, 2013 at 9:03 AM, Bogdan Iosif wrote:
>
I'm running on Windows so I can't use neither SysLog or logrotate (I think).
Do you know if OTRS holds a file lock on "otrs.log"?
Worst case I could write something that periodically checks this file's
size and when a threshold is reached it just moves it to some storage /
archive. I was hoping O
You don't have to use LogFile. You can use SysLog and handle that way, even
sending to Windows Event Viewer.
http://forums.otterhub.org/viewtopic.php?f=60&t=16826
Or just use logrotate.
On Tue, Mar 26, 2013 at 5:59 AM, Bogdan Iosif wrote:
> Hi list,
>
> I'm trying to keep the size of LogModul
Hi list,
I'm trying to keep the size of LogModule::LogFile in check in a better way
than allowed by configuring LogModule::LogFile::Date, which gives me
rollover to a new file every month.
A config that allows limiting the log file size (with overwrite when
threshold is reached or rolling over to
11 matches
Mail list logo
