> > 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. >
The ORACLE_HOME, TNS_ADMIN, LD_LIBRARY_PATH variables get set just before the rsyslogd is run. ORACLE_HOME is set to the production installation of our database - not to instantclinet's home. > > > > > > errors while building rsyslog's plugin omoracle: > > > 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? > The module got built and installed. It's just not loading. > > > > > > syslog entries when starting rsyslog daemon: > > 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/ > This error is interesting in its own, but since the omoracle plugin doesn't get loaded the $Om... parameters get ignored - as I can see from the debug output running rsyslog. > > > 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. > Not 100% sure, but I believe this is due to omoracle not loading. > > 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. > An interesting point. As I've mentioned before, these variables are set like this: export LD_LIBRARY_PATH=/usr/lib/oracle/10.2.0.4/client64/lib export PATH=/ust/lib/oracle/10.2.0.4/client64:/usr/local/bin:$PATH export TNS_ADMIN=/usr/lib/oracle/10.2.0.4/client64 export ORAENV_ASK=NO export ORACLE_SID=dbase . oraenv unset ORAENV_ASK ORACLE_HOME gets set via oraenv to the production database path - not instantclient's. The database in question is verison 11.2G, but this should not be a problem. Any help is much apprechiated. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
