NDOUtils 1.3.1 data sink error.

[Samba]

I first used command-line mysql to connect to the DB and manually add a
record using the mysql user and it worked.

I then tried using log2ndo on one of the archives to see if that would
work and I don't get any results back.  I looked into the Db and no
tables were modified.

Josh 

-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Joerg
Linge
Sent: Thursday, May 25, 2006 8:09 AM
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] NDOUtils 1.3.1 data sink error.

Am Donnerstag 25 Mai 2006 14:59 schrieb Samba:
> Joerg,

Hi Josh

> Great information!  I changed the config to write to file and it
works. 
> After changing it back I still get the same error.
>
> I checked and like you said I only see one ndo2db process.

OK, let me test this on my devel box. I will try to reproduxe this
error.

> One thing I questioned was the DB PREFIX option.  The default SQL
import
> used a prefix of ndo_, but the default in the config file is to not
use a
> prefix at all.  I've tried using both configs with no luck so I guess
> that's probably not it.

db_prefix must set to ndo_ if you use the default sheme.

can your db user write to the database ?
Please test this again, i have done the same mistakes by using a wrong
db 
user.

> I really appreciate your help and ideas.

Give me 5 minutes....


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null