Fwd: (RADIATOR) Incomplete entries in syslog

[Jan Tomasek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Mike,
> So... is our patch working OK?

I've bad news for you. It's working just partialy. Lots of messages ends where
they belongs too, but few are still corupted and delivered with wrong
facility. This time it looks like they might be too big for syslog-ng... but I
never before was experinced something things like this. Did you? Or were
mention it just as guess? If you think so, I can try to stress syslog-ng with
some huge text blocks.

I attached two files. In grep.messages.2004_09_01.log.bz2 are few examples of
corrupted messages. In radiator-file.bz2 are all uncorupted messages. I'm able
to reproduce this when I do intensive testing of PEAP-MSCHAPv2 or similar
method which causes big exchange of radius packets.

I will be thankfull for any ideas from you
- --
- --------------------------------------------------------------
Jan Tomasek aka Semik           work: CESNET, z.s.p.o.
http://www.tomasek.cz/                Zikova 4, 160 00 Praha 6
                                      Czech Republic
phone(work): +420 2 2435 5279         http://www.cesnet.cz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBOCTs79++DGvj6tMRApZLAJ4lDnSjFGpwQMT8Qvnv4TemvvgJeACfX41v
Xdv4VVZsn2EodoWNwKszdbs=
=K7EF
-----END PGP SIGNATURE-----

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.