On Thu, 2005-06-02 at 18:45 -0400, sean finney wrote: > tags 311695 unreproducible > thanks > > hi andres, > > On Thu, Jun 02, 2005 at 03:13:31PM -0400, Andres Salomon wrote: > > [1117732808] Error: Could not insert retention data for host 'gw' in > > table 'hostretention' > > [1117732808] Error: Could not insert retention data for host 'gw' in > > table 'hostretention' > > [1117732808] Error: Could not insert retention data for host 'gw' in > > table 'hostretention' > > [1117732808] Error: Could not insert retention data for host 'gw' in > > table 'hostretention' > > did you flush privileges after granting them? these error messages are
No, no.. See, nagios hadn't been configured yet. It was in whatever shape the package installs it as. There wasn't a nagios database, a nagios user, or any hosts/contacts/etc configured. There were separate mysql databases, and the default hosts/contacts/etc configured (that's where that 'gw' host comes from; it's one of the examples in the default configs). I really didn't do anything to nagios to get it to do this; just installed it. > usually from 'access denied' type messages. looking over the > README.mysql, it doesn't look like this is mentioned, but it is > definitely a necessary step. > > also, make sure that it's not some hung nagios process. if you have > multiple nagios processes, there's a chance that a previously hung > one from before when the access was granted is the culprit. you should > be able to just kill them There was only 1 nagios process. Something I forgot to mention, however; my attempt to kill it via init script (/etc/init.d/nagios stop) failed. I had to kill -9 it. -- Andres Salomon <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part