Problems after update 1.2.16

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Problems after update 1.2.16

Post by Trle94 »

Hello everyone,
So I have updated my cacti version from 1.2.14 or .13 do not remember exactly to 1.2.16.. First of all after graph sync graphs were working few more hours and after that it started showing that "Graphs Damaged" message...
So I tried fixing running cli script but nothing happened, after it I removed completely all graphs and recreated them... But still I have problems:

1. Some graphs are showing some not, and there is error on "real-time":
Screenshot_1.png
Screenshot_1.png (189.25 KiB) Viewed 1647 times
2. There are errors on devices since upgrade:
Screenshot_2.png
Screenshot_2.png (284.63 KiB) Viewed 1647 times
Please let me know what else I can do to try to get Cacti working as before...

3. There is error on Troubleshooting data source:
Screenshot_3.png
Screenshot_3.png (40.02 KiB) Viewed 1645 times
User avatar
Osiris
Cacti Guru User
Posts: 1424
Joined: Mon Jan 05, 2015 10:10 am

Re: Problems after update 1.2.16

Post by Osiris »

Not sure how you upgraded, but whatever you did you did it wrong. Normally, I just:

/bin/cp -rpf cacti-src/* cacti
chown -R apache:apache cacti

Then refresh the browser.
Before history, there was a paradise, now dust.
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Re: Problems after update 1.2.16

Post by Trle94 »

What has to do file permission with update?
You can see already from my third picture that file permissions are fine.
Update was done with 'yum update' its Centos.
After that i normally logged in to cacti and followed update page, that didnt show any error at all.
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Re: Problems after update 1.2.16

Post by Trle94 »

Hello,
Anyone willing to help me out?
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Problems after update 1.2.16

Post by cigamit »

Your getting invalid response messages in your logs. You should increase the logging level to see exactly what response you are getting for those data sources.
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Re: Problems after update 1.2.16

Post by Trle94 »

cigamit wrote: Wed Dec 09, 2020 1:20 pm Your getting invalid response messages in your logs. You should increase the logging level to see exactly what response you are getting for those data sources.
Hello,
I changed Generic Log Level to DEBUG, is it okay?
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Problems after update 1.2.16

Post by cigamit »

Probably too high, MEDIUM should show you results without all the extra noise.
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Re: Problems after update 1.2.16

Post by Trle94 »

cigamit wrote: Wed Dec 09, 2020 1:49 pm Probably too high, MEDIUM should show you results without all the extra noise.
Hello, here is what i got:
Screenshot_4.png
Screenshot_4.png (267.83 KiB) Viewed 1583 times
Screenshot_5.png
Screenshot_5.png (294.18 KiB) Viewed 1581 times
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Problems after update 1.2.16

Post by cigamit »

That shows that you are getting invalid results (we then show as U) back from the SNMP agent on the device. You might try querying the device via SNMP to one of the failed OIDs yourself to see if it is indeed the device. If the device does return the proper results on the command line, then you might using spine instead of cmd.php.
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Re: Problems after update 1.2.16

Post by Trle94 »

cigamit wrote: Wed Dec 09, 2020 2:14 pm That shows that you are getting invalid results (we then show as U) back from the SNMP agent on the device. You might try querying the device via SNMP to one of the failed OIDs yourself to see if it is indeed the device. If the device does return the proper results on the command line, then you might using spine instead of cmd.php.
Well its strange that it was working before, was there any changes within latest version that might affect that? Problem is even local machine where is hosted cacti is showing errors..

EDIT:

Code: Select all

snmpwalk -v 2c -c public localhost
SNMPv2-MIB::sysDescr.0 = STRING: Linux cacti.localhost 4.18.0-193.28.1.el8_2.x86_64 #1 SMP Thu Oct 22 00:20:22 UTC 2020 x86_64
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (19727119) 2 days, 6:47:51.19
SNMPv2-MIB::sysContact.0 = STRING: Root <root@localhost> (configure /etc/snmp/snmp.local.conf)
SNMPv2-MIB::sysName.0 = STRING: cacti.localhost
SNMPv2-MIB::sysLocation.0 = STRING: Unknown (edit /etc/snmp/snmpd.conf)
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (2) 0:00:00.02
SNMPv2-MIB::sysORID.1 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.2 = OID: SNMP-MPD-MIB::snmpMPDCompliance
SNMPv2-MIB::sysORID.3 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.5 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORID.6 = OID: TCP-MIB::tcpMIB
SNMPv2-MIB::sysORID.7 = OID: IP-MIB::ip
SNMPv2-MIB::sysORID.8 = OID: UDP-MIB::udpMIB
SNMPv2-MIB::sysORID.9 = OID: SNMP-NOTIFICATION-MIB::snmpNotifyFullCompliance
SNMPv2-MIB::sysORID.10 = OID: NOTIFICATION-LOG-MIB::notificationLogMIB
SNMPv2-MIB::sysORDescr.1 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.2 = STRING: The MIB for Message Processing and Dispatching.
SNMPv2-MIB::sysORDescr.3 = STRING: The management information definitions for the SNMP User-based Security Model.
SNMPv2-MIB::sysORDescr.4 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORDescr.5 = STRING: View-based Access Control Model for SNMP.
SNMPv2-MIB::sysORDescr.6 = STRING: The MIB module for managing TCP implementations
SNMPv2-MIB::sysORDescr.7 = STRING: The MIB module for managing IP and ICMP implementations
SNMPv2-MIB::sysORDescr.8 = STRING: The MIB module for managing UDP implementations
SNMPv2-MIB::sysORDescr.9 = STRING: The MIB modules for managing SNMP Notification, plus filtering.
SNMPv2-MIB::sysORDescr.10 = STRING: The MIB module for logging SNMP Notifications.
SNMPv2-MIB::sysORUpTime.1 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.2 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.3 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.4 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.5 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.6 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.7 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.8 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.9 = Timeticks: (2) 0:00:00.02
SNMPv2-MIB::sysORUpTime.10 = Timeticks: (2) 0:00:00.02
HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (19728407) 2 days, 6:48:04.07
HOST-RESOURCES-MIB::hrSystemUptime.0 = No more variables left in this MIB View (It is past the end of the MIB tree)
[root@cacti ~]# snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.2021.10.1.3.3
UCD-SNMP-MIB::laLoad.3 = No more variables left in this MIB View (It is past the end of the MIB tree)
It says No more variables left in this MIB View (It is past the end of the MIB tree)
So OID is wrong?

EDIT:
For Juniper SRX240:

Code: Select all

snmpwalk -v 2c -c public 10.10.10.1 .1.3.6.1.4.1.2021.11.7.0
UCD-SNMP-MIB::ssSysInterrupts.0 = No Such Object available on this agent at this OID
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Re: Problems after update 1.2.16

Post by Trle94 »

Hello,
Anyone willing to help me out? Problem is not resolved yet....
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Problems after update 1.2.16

Post by cigamit »

Did someone recently update the snmp configs on your devices? Because if an SNMPWALK is getting no information, then its not Cacti with the issue typically.
Trle94
Posts: 8
Joined: Mon Dec 07, 2020 9:10 am

Re: Problems after update 1.2.16

Post by Trle94 »

cigamit wrote: Sun Dec 13, 2020 1:25 am Did someone recently update the snmp configs on your devices? Because if an SNMPWALK is getting no information, then its not Cacti with the issue typically.
Hello,
As I said there was no updates on my devices just CACTI update from 1.2.14 to 1.2.16, no other changes were made. Even cacti localhost is complaining on some requests as you can see at begin of this topic..
cigamit
Developer
Posts: 3367
Joined: Thu Apr 07, 2005 3:29 pm
Location: B/CS Texas
Contact:

Re: Problems after update 1.2.16

Post by cigamit »

But as I said, if an SNMPWALK doesn't work, then its a problem with your devices. Not sure what else I can do to help, as snmpwalk isn't working. You need to check your snmp configs.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest