Re: No additional data after upgrade
Jaime Kikpole via cacti-user <[email protected]> Fri, 12 Oct 2018 21:52:56 -0400
| Newsgroups | gmane.network.cacti.user |
|---|---|
| Message-ID | <CA+sg5RSvct1U3L9j7f8PcKEdfpWbOfE=gwUOijxEyjpP6nOROg@mail.gmail.com> |
I just figured out how to get even more data in the logs. It looks like
Cacti is marking every devices as "Down" for some reason. It doesn't seem
to matter if I have them configured for "SNMP and Ping" or "SNMP or Ping".
Here is a section of the log from the most recent run:
2018/10/12 21:45:00 - POLLER: Poller[1] NOTE: Poller Int: '300', Cron
Int: '300', Time Since Last: '300.23', Max Runtime '298', Poller Runs:
'1'
2018/10/12 21:45:00 - POLLER: Poller[1] DEBUG: About to Spawn a Remote
Process [CMD: /usr/local/bin/php, ARGS: -q
"/usr/local/share/cacti/cmd.php" --poller=1 --first=0 --last=172
--mibs]
2018/10/12 21:45:00 - POLLER: Poller[1] DEBUG: About to Spawn a Remote
Process [CMD: /usr/local/bin/php, ARGS: -q
"/usr/local/share/cacti/cmd.php" --poller=1 --first=174 --last=174
--mibs]
2018/10/12 21:45:01 - POLLER: Poller[1] NOTE: There are no items in
your poller for this polling cycle!
2018/10/12 21:45:04 - PHPSVR DEBUG: SERVER: cmd
2018/10/12 21:45:04 - PHPSVR DEBUG: GETCWD: /usr/local/share/cacti
2018/10/12 21:45:04 - PHPSVR DEBUG: DIRNAM: /usr/local/share/cacti
2018/10/12 21:45:04 - PHPSVR DEBUG: FILENM:
/usr/local/share/cacti/script_server.php
2018/10/12 21:45:04 - PHPSVR PHP Script Server has Started - Parent is cmd
2018/10/12 21:45:04 - POLLER: Poller[1] PHP Script Server Started Properly
2018/10/12 21:45:04 - PING Device[42] PING: UDP ping error: Connection refused
2018/10/12 21:45:04 - POLLER: Poller[1] Device[42] STATUS: Device
'net1.cairodurham.org' is Down.
2018/10/12 21:45:04 - PING Device[83] PING: UDP ping error: Connection refused
2018/10/12 21:45:04 - POLLER: Poller[1] Device[83] STATUS: Device
'10.1.0.1' is Down.
2018/10/12 21:45:04 - PING Device[85] PING: UDP ping error: Connection refused
2018/10/12 21:45:04 - POLLER: Poller[1] Device[85] STATUS: Device
'10.1.0.60' is Down.
It goes on like that for a while, with those two lines ("UDP ping error"
and "Device ... is Down") for quite a few lines; possibly all devices.
Then it ends like this:
2018/10/12 21:45:06 - PING Device[172] PING: UDP ping error: Resource
temporarily unavailable
2018/10/12 21:45:07 - POLLER: Poller[1] Device[172] STATUS: Device
'10.1.90.8' is Down.
2018/10/12 21:45:07 - PHPSVR DEBUG: PHP Script Server Shutdown request
received, exiting
2018/10/12 21:45:07 - POLLER: Poller[1] Time: 6.4670 s, Poller: ,
Theads: N/A, Devices: 62
2018/10/12 21:45:07 - SYSTEM STATS: Time:6.7732 Method:cmd.php
Processes:1 Threads:N/A Hosts:63 HostsPerProcess:63 DataSources:14297
RRDsProcessed:0
2018/10/12 21:45:22 - POLLER: Poller[1] DEBUG: About to Spawn a Remote
Process [CMD: /usr/local/bin/php, ARGS: -q
/usr/local/share/cacti/poller_reports.php]
2018/10/12 21:45:22 - POLLER: Poller[1] DEBUG: About to Spawn a Remote
Process [CMD: /usr/local/bin/php, ARGS: -q
/usr/local/share/cacti/poller_spikekill.php]
2018/10/12 21:45:22 - POLLER: Poller[1] DEBUG: About to Spawn a Remote
Process [CMD: /usr/local/bin/php, ARGS: -q
/usr/local/share/cacti/poller_automation.php -M]
2018/10/12 21:45:22 - POLLER: Poller[1] DEBUG: About to Spawn a Remote
Process [CMD: /usr/local/bin/php, ARGS: -q
/usr/local/share/cacti/poller_maintenance.php]
I get the feeling that the device status has something to do with why data
isn't being logged, but I don't know why these devices are being assigned a
downed status. Any suggestions?
Jaime Kikpole
Director of Technology & Innovations
Cairo-Durham Central School District
(518) 622-8543, x59500
cairodurham.org <http://www.cairodurham.org>
Technical Support:
[email protected]
go.cairodurham.org/techtips
[image: Google Certified Educator, Level 1] [image: Google Certified
Educator, Level 2]
On Fri, Oct 12, 2018 at 9:08 PM Jaime Kikpole <[email protected]>
wrote:
> I just figured out how to run the poller with debug output. This is what
> I get. Any idea what it points to?
>
> # su -m cacti -c "/usr/local/bin/php /usr/local/share/cacti/poller.php --debug"
> s10/12/2018 20:59:46 - POLLER: Poller[1] NOTE: Poller Int: '300', Cron Int: '300', Time Since Last: '286.64', Max Runtime '298', Poller Runs: '1'
> 10/12/2018 20:59:46 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /usr/local/bin/php, ARGS: -q "/usr/local/share/cacti/cmd.php" --poller=1 --first=0 --last=172 --mibs]
> 10/12/2018 20:59:46 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /usr/local/bin/php, ARGS: -q "/usr/local/share/cacti/cmd.php" --poller=1 --first=174 --last=174 --mibs]
> Waiting on 2 of 2 pollers.
> Waiting on 1 of 2 pollers.
> Waiting on 1 of 2 pollers.
> Waiting on 1 of 2 pollers.
> Waiting on 1 of 2 pollers.
> 10/12/2018 20:59:53 - SYSTEM STATS: Time:6.5424 Method:cmd.php Processes:1 Threads:N/A Hosts:63 HostsPerProcess:63 DataSources:14297 RRDsProcessed:0
> 10/12/2018 21:00:23 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /usr/local/bin/php, ARGS: -q /usr/local/share/cacti/poller_reports.php]
> 10/12/2018 21:00:23 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /usr/local/bin/php, ARGS: -q /usr/local/share/cacti/poller_spikekill.php]
> 10/12/2018 21:00:23 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /usr/local/bin/php, ARGS: -q /usr/local/share/cacti/poller_automation.php -M]
> 10/12/2018 21:00:23 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /usr/local/bin/php, ARGS: -q /usr/local/share/cacti/poller_maintenance.php]
> #
>
>
>
--
This electronic message and any attachment(s) may contain confidential or
legally privileged information protected by law from further disclosure and
is intended only for the individual or entity identified above as the
addressee. If you are not the addressee (or the employee or agency
responsible to deliver it to the addressee), or if this message has been
addressed to you in error, you are hereby notified that you may not copy,
forward, disclose or use any part of this message or any attachment(s).
Please notify the sender immediately by return email or telephone and
permanently delete this message and attachment(s) from your system.