Hi all,
Found the solution.
It had to do with the syslog daemon running on Unix box (Solaris) with -t
option:
root 193 1 0 Feb 02 ? 0:38 /usr/sbin/syslogd -t
which does not allow messages coming from network:
from man: -t Disable the syslogd UPD port to turn off logging of
remote messages.
The fix was to restart syslog daemon without -t option:
daemon syslogd
Could we put this tip into the troubleshooting page?
Alex.
-----Original Message-----
From: Akoulov, Alexandre [IT]
Sent: Sunday, 13 February 2005 1:45 PM
To: Log4J Users List
Subject: RE: Cannot log into UNIX Syslog (with
org.apache.log4j.net.SyslogAppender)
Hi all,
I am still trying to solve "cannot log into UNIX Syslog" (please see original
email below). I've turned the log4j debug on (with the -Dlog4j.debug option)
and that is what I have
log4j: Parsing for [com.SSMB.EbbosDatabase.ErrorExternalLogger] with
value=[ERROR, SYSLOG].
log4j: Level token is [ERROR].
log4j: Category com.SSMB.EbbosDatabase.ErrorExternalLogger set to ERROR
log4j: Parsing appender named "SYSLOG".
log4j: Parsing layout options for "SYSLOG".
log4j: Setting property [conversionPattern] to [%d [%t] %-5p %c - %m%n].
log4j: End of parsing for "SYSLOG".
log4j: Setting property [syslogHost] to [localhost].
log4j: Setting property [facility] to [LOCAL5].
log4j: Parsed "SYSLOG" options.
As you can see all looks all right. What would you recommend I should do next?
I really need some help on how to solve this problem.
Thanks to all in advance,
Alex.
-----Original Message-----
From: Akoulov, Alexandre [IT]
Sent: Thursday, 10 February 2005 4:22 PM
To: [email protected]
Subject: Cannot log into UNIX Syslog
Hi all,
I am trying to log application error messages into syslog using log4j and so
far I have no success. I've read and searched a lot of information but could
not find an answer.
PROBLEM DESCRIPTION:
The application runs on the same machine as syslog. That is what my
log4j.properties file looks like:
===========================================================================
# Make root logger to log everything using A1 appender
log4j.rootLogger=DEBUG, A1
# This is an event logger that logs into a file
log4j.logger.com.SSMB.EbbosDatabase.InfoLogger=INFO, EVENT_FILE
# This an error logger that logs into a file
log4j.logger.com.SSMB.EbbosDatabase.ErrorLogger=ERROR, ERROR_FILE
# This is an error logger that logs into syslog
log4j.logger.com.SSMB.EbbosDatabase.SyslogLogger=ERROR, SYSLOG
.....<configuring appenders for A1, EVENT_FILE, ERROR_FILE>.....
# --SYSLOG--
log4j.appender.SYSLOG=org.apache.log4j.net.SyslogAppender
# Define a server where syslog lives
log4j.appender.SYSLOG.syslogHost=localhost
# Define a pipe (logging facility)
log4j.appender.SYSLOG.Facility=LOCAL5
# Uncomment the following line if need printed message to include the facility
name of the application
#log4j.appender.SYSLOG.FacilityPrinting=true
# Define message format
log4j.appender.SYSLOG.layout=org.apache.log4j.PatternLayout
# day thread warning level loggerName - message
log4j.appender.SYSLOG.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
===========================================================================
While file loggers (InfoLogger and ErrorLogger) log the messages into their
respective files, the syslog logger (SyslogLogger) does not:
===========================================================================
infoLogger.info("Test from info logger"); // successfully logs a message
errorLogger.error("Test from error logger"); // successfully logs a message
syslogLogger.error("Test from syslog logger"); // UNSUCCESSFUL :(
===========================================================================
On the same unix box I ran the following unix command in order to test whether
can log into syslog at all:
===========================================================================
logger -p local5.err "just testing syslog functionality"
===========================================================================
and it was successful - I could see this "just testing syslog functionality" in
a syslog file.
Thank you to all in advance for your thoughts on how to solve this problem.
Kind regards,
Alexandre Akoulov.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
