SysLogHandler is drivin me nuts

[michael]

Hi there,

I am stuck while trying to use the logging facilities. Its not logging
:-) Can somebody point me to a solution ?

The following snipplets are used

-------------------------------------------
"crap.py"

logging.config. fileConfig("log ging.cfg")
logger = logging.getLogg er ("syslog")
logger.info('Wh ile this is just chatty')

-------------------------------------------
"logging.cf g"

[syslog]
class=handlers. SysLogHandler
level=ERROR
formatters=form 01
facility=LOG_LO CAL0
priority = LOG_INFO

[formatters]
keys=form01

[formatter_form0 1]
format=%(leveln ame)s %(message)s

-------------------------------------------
"/etc/syslog.conf"

local0.*;local0 .!=debug /var/log/local.log
local0.=debug /var/log/local-d.log

Kind regards

Michael

[roderik]

michael wrote:

Hi there,

I am stuck while trying to use the logging facilities. Its not logging
:-) Can somebody point me to a solution ?

The following snipplets are used

-------------------------------------------
"crap.py"

logging.config. fileConfig("log ging.cfg")
logger = logging.getLogg er ("syslog")
logger.info('Wh ile this is just chatty')

-------------------------------------------
"logging.cf g"

[syslog]
class=handlers. SysLogHandler
level=ERROR
formatters=form 01
facility=LOG_LO CAL0
priority = LOG_INFO

[formatters]
keys=form01

[formatter_form0 1]
format=%(leveln ame)s %(message)s

-------------------------------------------
"/etc/syslog.conf"

local0.*;local0 .!=debug /var/log/local.log
local0.=debug /var/log/local-d.log

Kind regards

Michael

I'm taking a wild guess here(io. I haven't tested your code), but I
don't think you can expect a logger of level ERROR to logg messages of
level INFO. Try setting your log level to INFO.

regards
/rune

[Vinay Sajip]

michael wrote:

Hi there,

I am stuck while trying to use the logging facilities. Its not logging
:-) Can somebody point me to a solution ?

The following snipplets are used

-------------------------------------------
"crap.py"

logging.config. fileConfig("log ging.cfg")
logger = logging.getLogg er ("syslog")
logger.info('Wh ile this is just chatty')

-------------------------------------------
"logging.cf g"

[syslog]
class=handlers. SysLogHandler
level=ERROR
formatters=form 01
facility=LOG_LO CAL0
priority = LOG_INFO

[formatters]
keys=form01

[formatter_form0 1]
format=%(leveln ame)s %(message)s

-------------------------------------------
"/etc/syslog.conf"

local0.*;local0 .!=debug /var/log/local.log
local0.=debug /var/log/local-d.log

The config file appears incomplete - can you post the whole of it (if
it's not too big)? I would have expected to see lines like

[loggers]
keys=root

[handlers]
keys=syslog

[logger_root]
level=DEBUG
qualname=(root)
handlers=syslog

[handler_syslog]
class=handlers. SysLogHandler
level=ERROR
formatter=form0 1
host=localhost
port=handlers.S YSLOG_UDP_PORT
facility=LOG_LO CAL0
args=(('localho st', handlers.SYSLOG _UDP_PORT),
handlers.SysLog Handler.LOG_LOC AL0)

(the args line may wrap in this mail)

You can't encode the priority in the config file - it is automatically
determined from the logging level (e.g. INFO -> LOG_INFO).

Note that the SysLogHandler communicates with the syslog daemon via UDP
and there may be network problems preventing the messages getting to the
server. If in doubt, format a UDP packet and send directly from a Python
script (i.e. not via logging) to confirm that there is no network problem.

Best regards,
Vinay Sajip

[michael]

Vinay Sajip <vi*********@re d-dove.com> wrote in message news:<ma******* *************** *************** *@python.org>.. .

The config file appears incomplete - can you post the whole of it (if
it's not too big)? I would have expected to see lines like

Yep it was incomplete heres the complete config as it has to be

[loggers]
keys=root,syslo g

[handlers]
keys=syslog,fil e,stdout

[logger_syslog]
qualname=syslog
level=INFO
handlers=syslog

[logger_root]
qualname=root
level=INFO
handlers=stdout

[handler_syslog]
class=handlers. SysLogHandler
level=ERROR
formatter=syslo g
args=(('localho st', handlers.SYSLOG _UDP_PORT), handlers.SysLog Handler.LOG_USE R)

[handler_stdout]
class=StreamHan dler
level=INFO
formatter=stdou t
args=(sys.stdou t,)

[handler_file]
class=FileHandl er
level=INFO
formatter=stdou t
args=('python.l og', 'w')

[formatters]
keys=syslog,std out

[formatter_syslo g]
format=%(module )s %(levelname)s %(message)s

[formatter_stdou t]
format=%(module )s %(asctime)s %(levelname)s %(message)s

Thanks for the help

Michael

[Vinay Sajip]

michael wrote:

Yep it was incomplete heres the complete config as it has to be

[config file snipped]

The complete file looks OK. Did you take into account the comment
roderik made (about levels - does it work if you set the logger and
handler levels both to DEBUG)? And have you checked that there is no
network problem?

Best regards,

Vinay Sajip

[michael]

Vinay Sajip <vi*********@re d-dove.com> wrote in message news:<ma******* *************** *************** *@python.org>.. .

michael wrote:

Yep it was incomplete heres the complete config as it has to be

[config file snipped]

The complete file looks OK.

Thx. with this file it is working. The syslogd configuration under AIX was buggy.

regards

Michael

[Jan Dries]

Slightly OT, but regarding the title, shouldn't it be PEBKAC, since it's
keyboard and not ceyboard?

Regards,
Jan
michael wrote:

Vinay Sajip <vi*********@re d-dove.com> wrote in message news:<ma******* *************** *************** *@python.org>.. .

michael wrote:

Yep it was incomplete heres the complete config as it has to be

[config file snipped]

The complete file looks OK.

Thx. with this file it is working. The syslogd configuration under AIX was buggy.

regards

Michael

[Lloyd Zusman]

Jan Dries <ja*******@dcub e-resource.be> writes:

Slightly OT, but regarding the title, shouldn't it be PEBKAC, since it's
keyboard and not ceyboard?

Your computer didn't come with a ceyboard? :)

--
Lloyd Zusman
lj*@asfast.com
God bless you.

[Vinay Sajip]

Jan Dries <ja*******@dcub e-resource.be> wrote in message news:<ma******* *************** *************** *@python.org>.. .

Slightly OT, but regarding the title, shouldn't it be PEBKAC, since it's
keyboard and not ceyboard?

PEBCAC: Problem Exists Between Chair And Computer

[Jan Dries]

[Jan Dries]

Slightly OT, but regarding the title, shouldn't it be PEBKAC,
since it's
keyboard and not ceyboard?
[Vinay Sajip] PEBCAC: Problem Exists Between Chair And Computer

Interesting. I thought it was "Problem Exists Between Keyboard And Chair".
But this makes sensee too, of course. Nonetheless, Google has about 17000
references for PEBKAC, and only 381 for PEBCAC.

Regards,
Jan