When performing actions against Devices, replicated device information could sometimes be lost

[eschoeller]

I've been at this for about 5 hours now...

I upgraded to 1.2.15. My remote pollers stopped working. I could revive them by moving devices around. Then, they'd stop working again. Suddenly reporting "DataSources:0" but still having an accurate Host count. I then realized I could disable/enable the devices to get the remote pollers to collect data again. But this kept happening over and over again.

Finally I realized that it was only semi-intermittent enough and figured that it could be related to the boost process, since it too is something that runs intermittently. Sure enough, once the boost process ran, all the pollers went to having no data sources. And even after the boost process was complete, they never came back until I manually intervened. I reproduced this several times. Then I downgraded to 1.2.14. Everything is fine again, and I've seen several boost processes run and the remote pollers retain their data source polling.

Looking back through the extensive changelog for 1.2.15 I see numerous issues that could have triggered this. I'll let you guys take a first past on which issue this might be, since you'll probably zero in on it faster than I will. And I'm already spent on this.

Cheers!

[c0sm1n]

I'm experiencing the same issues after upgrading to 1.2.5. Remote poller processes all RRDs for about an hour and then stops without warning.
Moving all managed devices to the main poller and back 'fixes' it temporarily

2020/11/17 13:50:08 - SYSTEM STATS: Time:5.3593 Method:spine Processes:1 Threads:60 Hosts:13 HostsPerProcess:13 DataSources:1844 RRDsProcessed:0
2020/11/17 13:55:08 - SYSTEM STATS: Time:5.3588 Method:spine Processes:1 Threads:60 Hosts:13 HostsPerProcess:13 DataSources:1844 RRDsProcessed:0
2020/11/17 14:00:09 - SYSTEM STATS: Time:5.3579 Method:spine Processes:1 Threads:60 Hosts:13 HostsPerProcess:13 DataSources:1844 RRDsProcessed:0
2020/11/17 14:05:09 - SYSTEM STATS: Time:5.3673 Method:spine Processes:1 Threads:60 Hosts:13 HostsPerProcess:13 DataSources:1844 RRDsProcessed:0
2020/11/17 14:10:08 - SYSTEM STATS: Time:5.3485 Method:spine Processes:1 Threads:60 Hosts:13 HostsPerProcess:13 DataSources:1844 RRDsProcessed:0
2020/11/17 14:15:08 - SYSTEM STATS: Time:5.3571 Method:spine Processes:1 Threads:60 Hosts:13 HostsPerProcess:13 DataSources:1844 RRDsProcessed:0
2020/11/17 14:20:04 - SYSTEM STATS: Time:1.2630 Method:spine Processes:1 Threads:60 Hosts:15 HostsPerProcess:15 DataSources:0 RRDsProcessed:0
2020/11/17 14:25:04 - SYSTEM STATS: Time:1.2594 Method:spine Processes:1 Threads:60 Hosts:15 HostsPerProcess:15 DataSources:0 RRDsProcessed:0
2020/11/17 14:30:05 - SYSTEM STATS: Time:1.2619 Method:spine Processes:1 Threads:60 Hosts:15 HostsPerProcess:15 DataSources:0 RRDsProcessed:0
2020/11/17 14:35:04 - SYSTEM STATS: Time:1.2580 Method:spine Processes:1 Threads:60 Hosts:15 HostsPerProcess:15 DataSources:0 RRDsProcessed:0

[eschoeller]

Glad I'm not alone. Hopefully the fix is relatively easy.

[TheWitness]

I'll be looking at this over the weekend to try to reproduce. Day job is calling though.

[eschoeller]

Thanks!! Eric.

…

On Nov 20, 2020, at 7:41 AM, TheWitness ***@***.***> wrote:  I'll be looking at this over the weekend to try to reproduce. Day job is calling though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[TheWitness]

I'm still tracing this. I'm not quite sure what is breaking it yet.