Cacti (home)ForumsDocumentation
Cacti: offical forums and support
It is currently Sun Apr 21, 2019 5:54 pm

All times are UTC - 5 hours




Post new topic Reply to topic  [ 7 posts ] 
Author Message
 Post subject: 1.2.0 still has "Spike Kill" problems on FreeBSD
PostPosted: Thu Jan 10, 2019 9:37 am 
Offline

Joined: Wed Jan 06, 2010 10:04 pm
Posts: 11
Running from the packages and updated to 1.2.0 yesterday.

I had commented out the spike kill logic as referred to here due to the interaction with php72 that appeared to cause some problems: https://github.com/Cacti/cacti/issues/1663

This is marked "fixed".

It is not on FreeBSD under 1.2.0; as soon as I updated the problem came back (since the code files got updated again and my commented-out lines were of course re-activated.)

2019/01/10 08:25:00 - PING Device[16] SNMP: Device responded to SNMP
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] STATUS: Device 'ipgw-inside.d
enninger.net' is UP.
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] RECACHE: Processing 2 items i
n the auto reindex cache for 'ipgw-inside.denninger.net'.
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] DQ[1] RECACHE OID: .1.3.6.1.2
.1.1.3.0, (assert:5578105 < output:0:15:33:33.26)
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] DQ[1] RECACHE ASSERT FAILED '
5578105<0:15:33:33.26
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] NOTICE: Spike Kill in Effect
for 'ipgw-inside.denninger.net'.
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] DQ[9] RECACHE OID: .1.3.6.1.2
.1.1.3.0, (assert:5573660 < output:0:15:33:33.27)
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] DQ[9] RECACHE ASSERT FAILED '
5573660<0:15:33:33.27
2019/01/10 08:25:00 - POLLER: Poller[1] Device[16] NOTICE: Spike Kill in Effect
for 'ipgw-inside.denninger.net'.

Commenting out the lines referred to on Github once again restored the collection and graphing, but it's not really "fixed"; I'm just masking it.

Any ideas?


Top
 Profile  
 
 Post subject: Re: 1.2.0 still has "Spike Kill" problems on FreeBSD
PostPosted: Thu Jan 10, 2019 6:00 pm 
Offline
Cacti Pro User
User avatar

Joined: Mon Jan 05, 2015 10:10 am
Posts: 753
This may have more to do with php-snmp then it does with Cacti. Test with php-snmp uninstalled and provide feedback.

_________________
Before history, there was a paradise, now dust.


Top
 Profile  
 
 Post subject: Re: 1.2.0 still has "Spike Kill" problems on FreeBSD
PostPosted: Thu Jan 10, 2019 6:00 pm 
Offline
Cacti Pro User
User avatar

Joined: Mon Jan 05, 2015 10:10 am
Posts: 753
Also, state your version of php as well.

_________________
Before history, there was a paradise, now dust.


Top
 Profile  
 
 Post subject: Re: 1.2.0 still has "Spike Kill" problems on FreeBSD
PostPosted: Thu Jan 10, 2019 10:47 pm 
Offline

Joined: Wed Jan 06, 2010 10:04 pm
Posts: 11
PHP 7.2.13 (cli) (built: Dec 9 2018 01:14:11) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies

Building from packages (or ports, due to dependencies) I can't remove php-snmp because doing so removes cacti as it is listed as a direct dependency:

[email protected]:/disk/karl # pkg delete php72-snmp
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 2 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
php72-snmp-7.2.13
cacti-1.2.0

Number of packages to be removed: 2

The operation will free 50 MiB.

Proceed with deinstalling packages? [y/N]:

I can force that to be ignored and will attempt that -- is the consensus that I should request that FreeBSD not include the php-snmp module as a dependency (and in fact require it NOT be installed?)


Top
 Profile  
 
 Post subject: Re: 1.2.0 still has "Spike Kill" problems on FreeBSD
PostPosted: Fri Jan 11, 2019 1:57 pm 
Offline
Cacti Guru User

Joined: Sun Aug 27, 2017 12:05 am
Posts: 2391
It should be installed with Cacti but it should not mean cacti is uninstalled because of it. In most circumstances, the use of PHP-SNMP is generally OK but we have found certain people fair better with it removed. Alternatively, rather than uninstall the package, you could just disable the use of PHP-SNMP in the configuration (normally in /usr/local/etc/php/extensions.ini )

_________________
Official Cacti Developer

Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation

My resources:
How to submit Pull Requests
Development Wiki and How To's
Updated NetSNMP Memory template for Cacti 1.x
Cisco SFP template for Cacti 0.8.8


Top
 Profile  
 
 Post subject: Re: 1.2.0 still has "Spike Kill" problems on FreeBSD
PostPosted: Fri Jan 11, 2019 4:30 pm 
Offline
Cacti Pro User
User avatar

Joined: Mon Jan 05, 2015 10:10 am
Posts: 753
So, you need to disable quick print in the API when performing snmp get requests. Looks like PHP SNMP is fixing some of the deficiencies in more recent releases. Let me check a few things.

_________________
Before history, there was a paradise, now dust.


Top
 Profile  
 
 Post subject: Re: 1.2.0 still has "Spike Kill" problems on FreeBSD
PostPosted: Fri Jan 11, 2019 4:44 pm 
Offline
Cacti Pro User
User avatar

Joined: Mon Jan 05, 2015 10:10 am
Posts: 753
Edit lib/snmp.php, change line 74 from SNMP_VALUE_LIBRARY to SNMP_VALUE_PLAIN, then save the file. Problem solved I think.

_________________
Before history, there was a paradise, now dust.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group