Damjan Žiberna wrote: > I've installed oracle-instantclient-basic-10.2.0.4-1.x86_64 > and oracle-instantclient-devel-10.2.0.4-1.x86_64 and jdk-6u21-linux-x64. > I'm trying to use the rsyslog to send syslog messages to an existing oracle > db. I'm facing these problems, and don't really know where to begin. I've > setup the correct oracle environment during startup of the rsyslog and it > got me errors seen below. I have done the same trying to build the rsyslog > using "./configure --enable-oracle", then "make", "make install" with the > oracle environment setup, but got same errors seen below. > > Can anyone help me solve this?
I'm very much not up-to-date on Oracle, and I've never used instantclient. I've never tried to use rsyslog with Oracle either. Inline remarks [below] may therefore be wide of the mark. However it looks to me that you have a problem with your Oracle connect string; a problem with your rsyslog config; and a problem with your ORACLE_HOME. > > > errors while building rsyslog's plugin omoracle: > > make[2]: Entering directory > `/usr/src/rsyslog/rsyslog-5.4.0/plugins/omoracle' > CC omoracle_la-omoracle.lo > omoracle.c: In function ‘prepare_statement’: > omoracle.c:254: warning: pointer targets in passing argument 3 of > ‘OCIStmtPrepare’ differ in signedness > omoracle.c:268: warning: passing argument 4 of ‘OCIBindDynamic’ from > incompatible pointer type > omoracle.c: In function ‘createInstance’: > omoracle.c:301: warning: pointer targets in passing argument 1 of ‘strlen’ > differ in signedness > omoracle.c:301: warning: pointer targets in passing argument 1 of ‘__strdup’ > differ in signedness > omoracle.c: In function ‘log_detailed_err’: > omoracle.c:356: warning: passing argument 2 of ‘OCIHandleAlloc’ from > incompatible pointer type > omoracle.c:359: warning: passing argument 2 of ‘OCIHandleAlloc’ from > incompatible pointer type > omoracle.c:365: warning: passing argument 4 of ‘OCIParamGet’ from > incompatible pointer type > omoracle.c: In function ‘tryResume’: > omoracle.c:461: warning: pointer targets in passing argument 5 of > ‘OCISessionGet’ differ in signedness > omoracle.c: In function ‘startSession’: > omoracle.c:481: warning: pointer targets in passing argument 5 of > ‘OCISessionGet’ differ in signedness > omoracle.c: In function ‘parseSelectorAct’: > omoracle.c:517: warning: implicit declaration of function > ‘cflineParseTemplateName’ > CCLD omoracle.la > make[2]: Leaving directory `/usr/src/rsyslog/rsyslog-5.4.0/plugins/omoracle' > Making all in tests Those all look like warnings, not errors. Did the module get built? > > > syslog entries when starting rsyslog daemon: > > 2010-07-27T08:20:02.089573+02:00 paris kernel: imklog 5.4.0, log source = > /proc/kmsg started. > 2010-07-27T08:20:02.089665+02:00 paris rsyslogd: [origin software="rsyslogd" > swVersion="5.4.0" x-pid="11839" x-info="http://www.rsyslog.com";] start > 2010-07-27T08:20:02.074395+02:00 paris rsyslogd: Error message: ORA-12154: > TNS:could not resolve the connect identifier specified http://ora-12154.ora-code.com/ Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. > 2010-07-27T08:20:02.074413+02:00 paris rsyslogd: Unable to start Oracle > session > 2010-07-27T08:20:02.074430+02:00 paris rsyslogd: OCI INVALID HANDLE > 2010-07-27T08:20:02.074468+02:00 paris rsyslogd: the last error occured in > /etc/rsyslog.conf, line 19:"*.* :omoracle:;TestStmt" > 2010-07-27T08:20:02.089085+02:00 paris rsyslogd: warning: selector line > without actions will be discarded Defective rsyslog.conf. > 2010-07-27T08:20:02.089442+02:00 paris rsyslogd-2124: CONFIG ERROR: could > not interpret master config file '/etc/rsyslog.conf'. [try > http://www.rsyslog.com/e/2124 ] > > > Debug statements checking rsyslog's configuration: > > 1494.718276000:2abb22fc5ac0: cfline: '$ModLoad omoracle' > 1494.718290000:2abb22fc5ac0: Requested to load module 'omoracle' > 1494.718302000:2abb22fc5ac0: loading module > '/usr/local/lib/rsyslog/omoracle.so' > 1494.740232000:2abb22fc5ac0: Called LogError, msg: could not load module > '/usr/local/lib/rsyslog/omoracle.so', dlopen: /usr/lib/oracle/ > 10.2.0.4/client64/lib/libnnz10.so: undefined symbol: nltrc_entry http://old.nabble.com/Building-tora-2.0.0-0.3054svn.el5.src.rpm-on-FC9-td19979563.html The poster says: tora: symbol lookup error: /usr/lib/oracle/10.2.0.4/client/lib/libnnz10.so: undefined symbol: nltrc_entry [...] When I switch ORACLE_HOME to point to a full install of Oracle 10g, the problem goes away, and TOra launches normally. HTH, -- MrD. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
