Either the noclogd was started as a different user or the $nocolroot/run
directory is not writable by the process (or the previous noclogd.pid file
has a different user's permissions).
-vikas
Ron Parker wrote:
>
> Now I'm starting to get this hourly. What's the deal, and how to I
> correct it? Also, why did it just start happening after? The only
> other new element is that one of the machines being portmonitored went
> down earlier today, and that's when this started. I restarted the
> monitored and monitoring machines, and thats when this started. Any
> suggestions?
>
|