[resolved] graph icon links missing after upgrade ??

[Allen K]

Good day! I've been a Cacti user since before 2005, love it.. tired many others but always come back here..

I see weathermap is testing/working for 1.2.x now so I built a parallel server to test the upgrade process.. had a few issues, but no showstoppers aside from old templates/scripts/plugins that I removed all traces of.

the strange thing now, my graphs on 0.8.8h all had shortcut icons to the right of each graph:


the new install after moving the database/rra's and applicable scripts did show these icons last night, but now this morning they appear to be gone??


I've cleared cache, change php version from 8.1 to 8.0 (to clear weathermap errors) There isn't a single error in the logs.

Code: Select all

2023-08-07 12:38:09 - SYSTEM SYSLOG STATS: Time:0.02 Deletes:0 Incoming:0 Removes:0 XFers:0 Alerts:0 Alarms:0 Reports:0
2023-08-07 12:38:09 - POLLER: Poller[Main Poller] PID[578728] NOTE: Registering process! (syslog, master, 1, 578728)
2023-08-07 12:38:09 - SYSTEM MONITOR STATS: Time:0.01 Reboots:0 DownDevices:0 Notifications:0 Purges:0
2023-08-07 12:38:09 - SYSTEM THOLD STATS: Time:0.0146 Tholds:0 TotalDevices:39 DownDevices:16 NewDownDevices:0
2023-08-07 12:38:09 - SYSTEM STATS: WEATHERMAP Time:0.69 Maps:1 Warnings:0 Notes:None
2023-08-07 12:38:09 - WEATHERMAP MAPSTATS Time:0.68 MapId:25 MapFile:mGRE-VPN.conf Warnings:0
2023-08-07 12:38:09 - POLLER: Poller[Main Poller] PID[578702] NOTE: Registering process! (reports, master, 0, 578702)
2023-08-07 12:38:09 - SYSTEM MAINT STATS: Time:0.01
2023-08-07 12:38:09 - POLLER: Poller[Main Poller] PID[578708] NOTE: Registering process! (maintenance, master, 1, 578708)
2023-08-07 12:38:09 - POLLER: Poller[Main Poller] PID[578710] NOTE: Registering process! (rrdcheck, pmaster, 0, 578710)
2023-08-07 12:38:09 - SYSTEM DSSTATS STATS: Time:0.11 Type:HOURLY
2023-08-07 12:38:09 - POLLER: Poller[Main Poller] PID[578704] NOTE: Registering process! (spikekill, master, 0, 578704)
2023-08-07 12:38:09 - BOOST Local Data ID: 2244, Sorted Results: 0
2023-08-07 12:38:09 - BOOST Local Data ID: 2244, Archive Results: 0, Boost Results: 0
2023-08-07 12:38:09 - POLLER: Poller[Main Poller] PID[578700] NOTE: Registering process! (dsstats, pmaster, 0, 578700)
2023-08-07 12:38:09 - BOOST The RRDpath template is traffic_in:traffic_out
2023-08-07 12:38:09 - BOOST The RRDpath is /var/www/cacti/htdocs/rra//47/3714.rrd
2023-08-07 12:38:09 - BOOST Local Data ID: 3714, Sorted Results: 2
2023-08-07 12:38:09 - BOOST Local Data ID: 3714, Archive Results: 0, Boost Results: 2
2023-08-07 12:38:08 - SPINE: Poller[Main Poller] PID[578464] PT[140221047863104] Time: 7.1436 s, Threads: 15, Devices: 10
2023-08-07 12:38:08 - SYSTEM STATS: Time:6.9329 Method:spine Processes:5 Threads:15 Hosts:39 HostsPerProcess:8 DataSources:781 RRDsProcessed:0

I'm sure this was available last night, but gone this morning? I'm confused

edit: I've also discovered each graph is no longer a link to the daily/weekly/monthy/yearly view.

fresh/clean install of:
Ubuntu 22.04.3 LTS
PHP Version 8.0.29
Cacti Version 1.2.24 SPINE 1.2.24

[cigamit]

There is a permission under your User's Permissions

Screenshot_10.png (35.86 KiB) Viewed 592 times

[Allen K]

LOL omg... i looked everywhere.. spent 4 hours checking every section except for the profile permissions.. this didn't seem to carry over after a database update (not sure if it's something to look at for developers)

Thanks!

[cigamit]

It was suppose to default to on, we may have to look into why its not.

[TheWitness]

It's defaulted to on for the last couple of versions anyway.

[Allen K]

Hello, I have confirmed (at least for me) performing an upgrade either:

1. copying the old site to a new server, extracting the new 1.2.x branch over and running the upgrade process
2. fresh 1.2.x code, dumping the db, then adding to an empty one on the server and upgrading the DB

In both cases the option is not enabled. it is enabled on the old server.


I've found few other issues with upgrades and fatal errors (I think it might be better to catch as an exception and give the user a chance to correct it) Should I create a new thread for each or lump them all into one thread?

[TheWitness]

Create a bug on GitHub if you've in fact found a problem.