Simple Syslog Server

All-in-one implementation of RFC-5424 Syslog Protocol for testing purposes.

The server is based on syslog4j library.

There are 3 implemented server configurations:

• UDP
• TCP
• TLS (uses self-signed certificate)

The syslog server listens on port 9898 in all configurations.

Usage

java -jar simple-syslog-server.jar [udp|tcp|tls]

If no argument is provided, then the "tls" configuration is started.

Output

Console then contain output similar to:

Simple syslog server (RFC-5424)
Usage:
  java -jar simple-syslog-server.jar [protocol]

Possible protocols: udp, tcp, tls

No protocol provided. Defaulting to tls
Starting Simple Syslog Server
Protocol:     tls
Bind address: 0.0.0.0
Port:         9898
Creating Syslog server socket
Handling Syslog client /10.40.4.198
>>> Syslog message came: Rfc5424SyslogEvent [prioVersion=<12>1, facility=1, level=4, version=1, timestamp=2014-010-22T12:15:48.952+02:00, host=my-nb, appName=Test, procId=11119, msgId=-, structuredData=-, message=Message one]
>>> Syslog message came: Rfc5424SyslogEvent [prioVersion=<12>1, facility=1, level=4, version=1, timestamp=2014-010-22T12:15:52.039+02:00, host=my-nb, appName=Test, procId=11119, msgId=-, structuredData=-, message=Message two]

Testing

The format of Syslog messages is specified by the RFC-5424

To test the syslog server, you can either use the logger Linux command:

logger --tcp -n localhost -P 9898 "Test message"

or try directly one of example messages specified in the RFC:

nc -w0 localhost 9898 <<< "<34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47 - BOM'su root' failed for lonvick on /dev/pts/8"

License

• GNU Lesser General Public License Version 2.1