I have Tomcat installed on a Unix box and I need to start it remotely from another Unix box.
Tomcat is started using a script. When this script is run locally everything is fine. When I run the same script from remote box, tomcat starts but the command running the script does not terminate.:(
... (2 Replies)
Hi all,
I Installed Tomcat in an remote linux server (/usr/tomcat)and start service, using ./startup.sh (and tried with ./catalina.sh too).
//----------------------------------------------------------------//
# ./startup.sh
Using CATALINA_BASE: /usr/tomcat/apache-tomcat-6.0.16/
Using... (1 Reply)
Hi All,
I need to send all apache logs to local syslog and then to syslog server (STRM – Security Threat response manager).
I follow these steps:-
vi /etc/httpd/conf/httpd.conf
Added these lines :-
ErrorLog syslog:local1
LogLevel notice
Then in syslog.conf:-
local1.crit... (3 Replies)
Hello Forumers!
Has anyone successfully implemented forwarding of syslog messages to a remote server which is listening on a port other than udp514?
Thanks! (3 Replies)
Hi All,
I have several Tomcat 7.0.12 installations on remote servers for different projects. I need to start and stop them from a centralized server. Once I start the server remotely using ssh commands, server starts successfully but prompt does not exit. It keeps on holding.
I have... (4 Replies)
Hi Gurus,
Our tomcat server was found hanging and responding to requests although ports 8080 & 8009(AJP) were found in listening state. The catalina.out had the below output:
We have JavaMelody(Monitoring tool) packaged along with our application and it seems that monitoring through... (3 Replies)
Hello All,
Server: SUSE Linux Enterprise Server 11.3 (x86_64)
Syslog-ng Version: syslog-ng 2.0.9
We have configured a Cisco router to send it's log messages to this server listed above. This has been working just perfectly
for the last couple months, but we had never setup the log... (9 Replies)
I have a script, which connecting to remote server and first checks, if the files are there by timestamp. If not I want the script exit without error. Below is a code
TARFILE=${NAME}.tar
TARGZFILE=${NAME}.tar.gz
ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;... (3 Replies)
Discussion started by: digioleg54
3 Replies
LEARN ABOUT DEBIAN
log::log4perl::appender::limit
Appender::Limit(3pm) User Contributed Perl Documentation Appender::Limit(3pm)NAME
Log::Log4perl::Appender::Limit - Limit message delivery via block period
SYNOPSIS
use Log::Log4perl qw(:easy);
my $conf = qq(
log4perl.category = WARN, Limiter
# Email appender
log4perl.appender.Mailer = Log::Dispatch::Email::MailSend
log4perl.appender.Mailer.to = drone@pageme.com
log4perl.appender.Mailer.subject = Something's broken!
log4perl.appender.Mailer.buffered = 0
log4perl.appender.Mailer.layout = PatternLayout
log4perl.appender.Mailer.layout.ConversionPattern=%d %m %n
# Limiting appender, using the email appender above
log4perl.appender.Limiter = Log::Log4perl::Appender::Limit
log4perl.appender.Limiter.appender = Mailer
log4perl.appender.Limiter.block_period = 3600
);
Log::Log4perl->init($conf);
WARN("This message will be sent immediately");
WARN("This message will be delayed by one hour.");
sleep(3601);
WARN("This message plus the last one will be sent now");
DESCRIPTION
"appender"
Specifies the name of the appender used by the limiter. The appender specified must be defined somewhere in the configuration file, not
necessarily before the definition of "Log::Log4perl::Appender::Limit".
"block_period"
Period in seconds between delivery of messages. If messages arrive in between, they will be either saved (if "accumulate" is set to a
true value) or discarded (if "accumulate" isn't set).
"persistent"
File name in which "Log::Log4perl::Appender::Limit" persistently stores delivery times. If omitted, the appender will have no
recollection of what happened when the program restarts.
"max_until_flushed"
Maximum number of accumulated messages. If exceeded, the appender flushes all messages, regardless if the interval set in
"block_period" has passed or not. Don't mix with "max_until_discarded".
"max_until_discarded"
Maximum number of accumulated messages. If exceeded, the appender will simply discard additional messages, waiting for "block_period"
to expire to flush all accumulated messages. Don't mix with "max_until_flushed".
If the appender attached to "Limit" uses "PatternLayout" with a timestamp specifier, you will notice that the message timestamps are
reflecting the original log event, not the time of the message rendering in the attached appender. Major trickery has been applied to
accomplish this (Cough!).
DEVELOPMENT NOTES
"Log::Log4perl::Appender::Limit" is a composite appender. Unlike other appenders, it doesn't log any messages, it just passes them on to
its attached sub-appender. For this reason, it doesn't need a layout (contrary to regular appenders). If it defines none, messages are
passed on unaltered.
Custom filters are also applied to the composite appender only. They are not applied to the sub-appender. Same applies to appender
thresholds. This behaviour might change in the future.
COPYRIGHT AND LICENSE
Copyright 2002-2009 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2010-07-21 Appender::Limit(3pm)