Hello All

Hoping everyone would be doing great, I am trying to send Logs between two
systems, System 1 and System 2 through TLS using RELP, I am using the
http://www.rsyslog.com/using-tls-with-relp/ as my guide. but I
unfortunately I am not able to transfer my logs from System 1 to System 2.

******* My System 1 ********

*system1:~# rsyslogd -version*
rsyslogd 7.5.7, compiled with:
        FEATURE_REGEXP:                         Yes
        FEATURE_LARGEFILE:                      No
        GSSAPI Kerberos 5 support:              Yes
        FEATURE_DEBUG (debug build, slow code): No
        32bit Atomic operations supported:      Yes
        64bit Atomic operations supported:      Yes
        Runtime Instrumentation (slow code):    No
        uuid support:                           Yes
        Number of Bits in RainerScript integers: 32 (due to too-old json-c
lib)

See http://www.rsyslog.com for more information.

*system 1:~# rsyslogd -N1*
rsyslogd: version 7.5.7, config validation run (level 1), master config
/etc/rsyslog.conf
rsyslogd: warning: ~ action is deprecated, consider using the 'stop'
statement instead [try http://www.rsyslog.com/e/2307 ]
.
.
rsyslogd: imtcp: module loaded, but no listeners defined - no input will be
gathered [try http://www.rsyslog.com/e/2212 ]
rsyslogd: End of config validation run. Bye.

Means No Error

******* System 2 ********

asergLogger:~ # rsyslogd -version

rsyslogd 7.5.7, compiled with:
        FEATURE_REGEXP:                         Yes
        FEATURE_LARGEFILE:                      No
        GSSAPI Kerberos 5 support:              No
        FEATURE_DEBUG (debug build, slow code): No
        32bit Atomic operations supported:      Yes
        64bit Atomic operations supported:      Yes
        Runtime Instrumentation (slow code):    No
        uuid support:                           Yes
        Number of Bits in RainerScript integers: 32 (due to too-old json-c
lib)

See http://www.rsyslog.com for more information.

*system2:~ # rsyslogd -N1*
rsyslogd: version 7.5.7, config validation run (level 1), master config
/etc/rsyslog.conf
rsyslogd: warning: ~ action is deprecated, consider using the 'stop'
statement instead [try http://www.rsyslog.com/e/2307 ]
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line
177: syntax error on token '" tls.caCert=' [try
http://www.rsyslog.com/e/2207 ]
rsyslogd: CONFIG ERROR: could not interpret master config file
'/etc/rsyslog.conf'. [try http://www.rsyslog.com/e/2207 ]
rsyslogd: run failed with error -2207 (see rsyslog.h or try
http://www.rsyslog.com/e/2207 to learn what that number means)

The Same Syntax on which its generating error is working fine on system1.

Note: I compiled rsyslog on system from source and added additional
features such as Digital Signature but that will be on later stages, so far
I am not even able to transfer logs on tls.

Attachments: Rsyslog.conf from System 1 and Rsyslog.conf from System 2

I dont know whether I am making any error or its version's problem as I
already have jumped between many versions, first to v8-devel, then to v7.4
as they both dont support RELP, I have settled with v7.5.

Regards

-- 
*Waqar Afridi*

waqarafridi.wordpress.com
http://pk.linkedin.com/pub/waqar-afridi/15/98/494
http://imsciences.edu.pk/serg/2010/10/waqar-afridi/

Member CSRDU
http://csrdu.org/ <http://csrdu.org/blog/people/>

Attachment: rsyslog.conf_system1
Description: Binary data

Attachment: rsyslog.conf_system2
Description: Binary data

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to