Restarted server and got OID generation failed (DBD ERROR:
Restarted server and got OID generation failed (DBD ERROR:
So i restarted the server and all the oracle DB server had alerts coming up all saying this error
OID generation failed (DBD ERROR: OCISessionBegin)
I also noticed this error in the logs
2015-05-11 13:26:09ndomod: Error writing to data sink! Some output may get lost...
OID generation failed (DBD ERROR: OCISessionBegin)
I also noticed this error in the logs
2015-05-11 13:26:09ndomod: Error writing to data sink! Some output may get lost...
Re: Restarted server and got OID generation failed (DBD ERR
Post the output of these commands:
Post or PM me the content of your /etc/hosts.
Code: Select all
service ndo2db status
Code: Select all
hostnameRe: Restarted server and got OID generation failed (DBD ERR
you want the outputs from nagios server or the DB clients?
On the nagios server /etc/hosts is empty as in default
ndo2db us running and
hostname is nagiosxi.cfjh.org
Nagios log says this
ndomod: Error writing to data sink! Some output may get lost...
ndomod: Please check remote ndo2db log, database connection or SSL Parameters
On the nagios server /etc/hosts is empty as in default
ndo2db us running and
hostname is nagiosxi.cfjh.org
Nagios log says this
ndomod: Error writing to data sink! Some output may get lost...
ndomod: Please check remote ndo2db log, database connection or SSL Parameters
Re: Restarted server and got OID generation failed (DBD ERR
/etc/hosts should have:
If that's not in there, add it and restart nagios and ndo2db.
Code: Select all
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4Code: Select all
service nagios stop
service ndo2db restart
service nagios startRe: Restarted server and got OID generation failed (DBD ERR
ya that is the only thing in hosts
when i did ndo2db i got cannot open /usr/local/nagios/var/ndo2db.lock for reading: no such file or directory
when i did ndo2db i got cannot open /usr/local/nagios/var/ndo2db.lock for reading: no such file or directory
Last edited by gdolidze on Mon May 11, 2015 3:28 pm, edited 1 time in total.
Re: Restarted server and got OID generation failed (DBD ERR
Is MySQL local or offloaded to a remote server? Can you show us the "/usr/local/nagios/etc/ndo2db.cfg" file? Hide sensitive info.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Restarted server and got OID generation failed (DBD ERR
everything is remote.
Code: Select all
ck_file=/usr/local/nagios/var/ndo2db.lock
ndo2db_user=nagios
ndo2db_group=nagios
socket_type=unix
socket_name=/usr/local/nagios/var/ndo.sock
tcp_port=5668
db_servertype=mysql
db_host=localhost
db_port=3306
db_name=nagios
db_prefix=nagios_
db_user=ndoutils
db_pass=n@gweb
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Restarted server and got OID generation failed (DBD ERR
This indicates otherwise:gdolidze wrote:everything is remote.
Are you sure?gdolidze wrote:Code: Select all
db_host=localhost db_port=3306
Re: Restarted server and got OID generation failed (DBD ERR
I am monitoring remote server which have DB on it.
after a simple restart i got this error, i tried restoring but didn't work.
after a simple restart i got this error, i tried restoring but didn't work.
Last edited by gdolidze on Mon May 11, 2015 3:56 pm, edited 1 time in total.
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Restarted server and got OID generation failed (DBD ERR
I'd be alarmed about how the configuration got changed. This is the document that outlines the process of offloading the db:
http://assets.nagios.com/downloads/nagi ... Server.pdf
I would review all the parts of that document before making any change, and furthermore I'd make a close analysis to identify why the problem came up in the first place. Rebooting a server shouldn't make changes to a cfg file.
http://assets.nagios.com/downloads/nagi ... Server.pdf
I would review all the parts of that document before making any change, and furthermore I'd make a close analysis to identify why the problem came up in the first place. Rebooting a server shouldn't make changes to a cfg file.