Search found 34 matches

by warben61
Wed Jun 22, 2022 5:00 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Will do, thanks. I'll turn on a few each day until the problem shows up again.
by warben61
Wed Jun 22, 2022 4:45 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Hmm. Well, let me know if you want me to test anything. I'm content letting the system run as it sits right now still with no errors after that change. And of course we're happy to see complete graphs again :) No breaks after 8am today.
Graph example.PNG
Graph example.PNG (47.2 KiB) Viewed 481 times
by warben61
Wed Jun 22, 2022 1:06 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Cool. I have a list of the 40 device IDs that were changed from 5 thread to 1. I can put them back to 5 to test.
by warben61
Wed Jun 22, 2022 1:00 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Actually I mis-spoke. I didn't just change that one, I changed all that have been added. I thought I remembered my query only hit that one device but I changed all 40 rows. update host set device_threads = '1' where device_threads != '1'; The statements in my previous post though don't change. The o...
by warben61
Wed Jun 22, 2022 11:50 am
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

It's a Miktrotik router, HapLite, Board name RB941-2nD. We've got 2000+ of these being polled. After the change, this host looks identical to all the rest. The only thing I changed was the number of collection threads earlier today. All we're monitoring is traffic rate on port 1. SNMPv3, SHA, AES-12...
by warben61
Wed Jun 22, 2022 11:27 am
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

I'm cautiously optimistic that I've found one single host causing the problem. I found this thread: https://forums.cacti.net/viewtopic.php?t=53496 The last comment talks about setting collection threads to 1. I did a query on the database and found 40 hosts that were set to 5 threads. 39 of them had...
by warben61
Tue Jun 21, 2022 8:23 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

I've gotta get offline for now. Tomorrow I might mass disable a whole bunch of hosts and start adding back to see if it's a problem with something. Actually that brings up a question. Does the poller process devices in any certain order? I think I've noticed that devices added a long time ago always...
by warben61
Tue Jun 21, 2022 8:04 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

It didn't like that. Weird though - the test runs go fine. But as soon as the poller runs, it fails. I had to back out of that one because I wasn't getting any good poll cycles.
by warben61
Tue Jun 21, 2022 7:25 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Hmm that may be a red herring. I've run it a few more times and this was the latest ending: Total[41.7185] Device[3364] HT[1] DS[38065] TT[21.20] SCRIPT: perl /usr/share/cacti/site/scripts/ping.pl 'x.x.x.x', output: 14.1 Total[41.7197] Device[1122] Checking for System Information Update Total[41.719...
by warben61
Tue Jun 21, 2022 7:20 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

As far as I can tell it's totally random. The number of RRDs processed is different anytime so to me that makes it sound like it's stopping at different spots. I ran that command... it runs just fine. Wait, here's something. I ran this command: /usr/local/spine/bin/spine -R -S -V 3 Found that from a...
by warben61
Tue Jun 21, 2022 6:04 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Alrighty. There's no noticeable difference in running with snmp_host_cleanup commented out. I just pulled the latest spine and have that installed now.
by warben61
Tue Jun 21, 2022 4:11 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

That's gonna be interesting to track down. Yeah, no results on that query. mysql> SELECT host_id, COUNT(DISTINCT CONCAT(snmp_username, snmp_password, snmp_auth_protocol, snmp_priv_passphrase, snmp_priv_protocol, snmp_context, snmp_engine_id)) AS `combos` FROM poller_item WHERE snmp_priv_protocol='AE...
by warben61
Tue Jun 21, 2022 3:42 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Poller interval is 5 minutes. Typical runtime is 20-30 seconds.
by warben61
Tue Jun 21, 2022 3:33 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

2710 hosts at AES128. We did notice there are some new options in the dropdowns like AES128, 192, 256, whereas before we just chose AES. Same for SHA. I haven't seen any problems with the defaults though and I've just had our guys using AES128 since it seems to connect to our Mikrotiks no problem. m...
by warben61
Tue Jun 21, 2022 3:24 pm
Forum: Help: Linux/Unix Specific
Topic: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded
Replies: 64
Views: 3655

Re: Upgrade 1.2.18 to 1.2.21 - Error: Maximum runtime of 298 seconds exceeded

Results below. The blank row made me curious... so I did the next queries as well. The blank rows are all from hosts not using snmpv3. Not sure if that has anything to do with anything, but I figured I'd include that too. mysql> select distinct snmp_auth_protocol, snmp_priv_protocol from host; +----...