MonitorWare Knowledge Base

[GordT.]

I'm playing with RFC3195 on WinSyslog 6.1.420 (using LOGGER as my test agent), and running into an oddity. Evne though the Listener Port is available, RFC3195 insists on always using port 601. Is this expected as part of RFC compliance? I can't find any docs on this.

Not sure if this is different on WinSyslog 7 and I don't have the luxury of testing on this version - my dev server needs to remain 6.1 to match production right now because I'm switching production servers and need to keep a reasonably consistent production template until the move is done.

[mmeckelein]

Hello,

This is a bug of a previous liblogging version.

Implemented the new LibLogging Version ( 0.6.0 ). In previous versions changing the listening port from 601 to any other in RFC3195 format does not take affect. This is fixed now.

http://www.winsyslog.com/Common/en/Vers ... log7.0.php

This fixed version was implemented in WinSyslog 7. Therefore an upgrade is required. Sorry that I have no better answer at hand.

Best regards,
Michael Meckelein
Adiscon

[lorinc]

Hi,

I try to connect to you listener via the rfc3195 configured on port 601with your logging client.

I see a tcp service listening on the 601 port

Code: Select all

TCP    0.0.0.0:601            0.0.0.0:0              LISTENING

but when I start the logger client it just blocked and never returning

Code: Select all

c:\Temp\logger(2)>logger.exe -a 601 -m 3195raw message
Adiscon logger V1.2 - see www.monitorware.com/logger/ for details.
Logging to 127.0.0.1:601

By the way the tcp and udp protocol working perfectly.
I written also a simple java program based on beepcore with that
during the call of

Code: Select all

session = TCPSessionCreator.initiate(host, port);

I got the following error:
ep 8, 2006 11:55:28 PM org.beepcore.beep.core.SessionImpl terminate

Code: Select all

SEVERE: Problem with RPY: Invalid content type for this message
SyslogRaw: Error connecting to 127.0.0.1:601
   Greeting exchange failed

Could you help me what can be the problem?

Thanks in advance!
Lorinc

[lorinc]

I just forgot the version: 7.1.434
I don't see bugfixes in this topic in your latest beta

[lorinc]

Same with 7.2.437, the default listener started for RFC3195 on the given port, but the client (Adiscon Logger V1.2) just stopping in the sending state

Code: Select all

c:\Temp\logger>logger.exe -a 601 -l localhost -m 3195raw mymessage
Adiscon logger V1.2 - see www.monitorware.com/logger/ for details.
Logging to localhost:601
_


Can anybody help me?

Lorinc

[alorbach]

Hi,

I will take a look into it and try to reproduce. It will take a little while.

regards,
Andre

[alorbach]

Hi,

we have recompiled the logger application with the latest liblogging successfully, and updated the logger.zip archive from here:
http://www.monitorware.com/en/logger/index.php

There was a problem like you described when the loghost and sender where the same machine. In my test environments, it works now also if sender and receiver are the same machine.

best regards,
Andre Lorbach

[lorinc]

Thanks Andre!

It's working for me (with the v1.3 logger) too.

Regards,
Lorinc