David,
It should work anyway, the new poller will run and stay up for a long time, it
will no show any meaningful output regarding the interfaces.
Javier
David Lesaffre wrote:
> Worked it out.
>
> Use the old poller.php to repopulate the database.
> Once it has run, return to the new poller2.ph
Worked it out.
Use the old poller.php to repopulate the database.
Once it has run, return to the new poller2.php, et voilà
On Wed, 2005-06-15 at 10:45 +0200, David Lesaffre wrote:
Nothing yet.
Steps taken:
# crontab -u jffnms -e
# /etc/init.d/cron reload
# pkil
Nothing yet.
Steps taken:
# crontab -u jffnms -e
# /etc/init.d/cron reload
# pkill php
# pgrep php
#
-> So, no php processes running
new poller:
# su - jffnms -c "cd /opt/jffnms/engine && /usr/bin/php poller2.php master 5"
Process Already Running.
# ps -fp $(pgrep php)
UID PID PPID
Some of the extensions were defined twice in
/etc/php4/cli/php.ini
After correcting:
# su - jffnms -c "cd /opt/jffnms/engine && /usr/bin/php -q poller2.php master 5"
Process Already Running.
Now I'm waiting to see some results.
On Wed, 2005-06-15 at 09:58 +0200, David Lesaffre wrote:
St
Still no succes
But running the poller manually gives
# su - jffnms -c "cd /opt/jffnms/engine && /usr/bin/php -q poller2.php master 5"
PHP Warning: Function registration failed - duplicate name - mysql_connect in Unknown on line 0
PHP Warning: Function registration failed - duplicate name -
David,
Check that your crond is running then.
And also you may need to clear the events/alarm tables if the date difference
was real big.
And maybe do a SQL command: "UPDATE interfaces set last_poll_date = 0;" to clear
the last_poll_date field.
Javier
David Lesaffre wrote:
> After a reboot, we
After a reboot, we now get the "Login successful" messages and syslog messages, but that's it.
No events on an interface (any interface) going down.
On Mon, 2005-06-13 at 13:14 -0300, Javier Szyszlican wrote:
David,
If you changed the date on your server you should restart Apache too (and a
David,
If you changed the date on your server you should restart Apache too (and all
the processes that keep track of time), well, a reboot is better.
Javier
David Lesaffre wrote:
> The date was way off on my JFFNMS machine. It was more than a month
> ahead of the real time.
>
> So, I've reset
The date was way off on my JFFNMS machine. It was more than a month ahead of the real time.
So, I've reset the clock.
JFFNMS didn't show any new events, but that seems reasonable:
if it shows the most recent events, then the events that occured in the future will be shown, not the new ones, b
