Error - /opt/librenms/cronic /opt/librenms/poller-wrapper.py 23

Good Morning,

Ever since my system updated this morning I have been getting these alerts -

Ideas?

-Mike

Cronic detected failure or error output for the command:
/opt/librenms/poller-wrapper.py 23

RESULT CODE: 2

ERROR OUTPUT:

STANDARD OUTPUT:
INFO: starting the poller at 2018-03-02 09:45:52 with 23 threads, slowest devices first
INFO: worker Thread-22 finished device 180 in 99 seconds
INFO: worker Thread-21 finished device 183 in 177 seconds
INFO: worker Thread-23 finished device 181 in 177 seconds
INFO: worker Thread-20 finished device 9 in 186 seconds
INFO: worker Thread-19 finished device 158 in 195 seconds
INFO: worker Thread-18 finished device 157 in 196 seconds
INFO: worker Thread-17 finished device 154 in 201 seconds
INFO: worker Thread-16 finished device 156 in 202 seconds
INFO: worker Thread-15 finished device 8 in 204 seconds
INFO: worker Thread-13 finished device 185 in 209 seconds
INFO: worker Thread-14 finished device 162 in 210 seconds
INFO: worker Thread-12 finished device 161 in 210 seconds
INFO: worker Thread-11 finished device 160 in 286 seconds
INFO: worker Thread-9 finished device 159 in 286 seconds
INFO: worker Thread-10 finished device 151 in 286 seconds
INFO: worker Thread-15 finished device 28 in 82 seconds
INFO: worker Thread-21 finished device 172 in 110 seconds
INFO: worker Thread-22 finished device 182 in 194 seconds
INFO: worker Thread-18 finished device 153 in 98 seconds
INFO: worker Thread-23 finished device 21 in 121 seconds
INFO: worker Thread-20 finished device 147 in 114 seconds
INFO: worker Thread-12 finished device 3 in 90 seconds
INFO: worker Thread-16 finished device 25 in 99 seconds
WARNING: worker Thread-7 finished device 167 in 302 seconds
INFO: worker Thread-10 finished device 98 in 19 seconds
INFO: worker Thread-15 finished device 130 in 19 seconds
WARNING: worker Thread-8 finished device 149 in 306 seconds
INFO: worker Thread-9 finished device 44 in 20 seconds
INFO: worker Thread-17 finished device 179 in 106 seconds
WARNING: worker Thread-6 finished device 18 in 310 seconds
INFO: worker Thread-21 finished device 171 in 22 seconds
INFO: worker Thread-22 finished device 65 in 16 seconds
INFO: worker Thread-11 finished device 168 in 25 seconds
INFO: worker Thread-14 finished device 152 in 102 seconds
INFO: worker Thread-18 finished device 52 in 17 seconds
INFO: worker Thread-12 finished device 50 in 11 seconds
INFO: worker Thread-20 finished device 73 in 15 seconds
INFO: worker Thread-10 finished device 71 in 12 seconds
WARNING: worker Thread-5 finished device 138 in 319 seconds
INFO: worker Thread-15 finished device 128 in 13 seconds
INFO: worker Thread-16 finished device 42 in 19 seconds
INFO: worker Thread-19 finished device 186 in 149 seconds
INFO: worker Thread-9 finished device 93 in 65 seconds
INFO: worker Thread-17 finished device 76 in 69 seconds
INFO: worker Thread-13 finished device 37 in 168 seconds
INFO: worker Thread-11 finished device 112 in 68 seconds
INFO: worker Thread-6 finished device 113 in 75 seconds
INFO: worker Thread-21 finished device 53 in 75 seconds
INFO: worker Thread-8 finished device 131 in 80 seconds
INFO: worker Thread-22 finished device 45 in 100 seconds
INFO: worker Thread-14 finished device 90 in 102 seconds
INFO: worker Thread-12 finished device 66 in 122 seconds
INFO: worker Thread-20 finished device 75 in 148 seconds
INFO: worker Thread-23 finished device 148 in 165 seconds
INFO: worker Thread-10 finished device 70 in 149 seconds
INFO: worker Thread-16 finished device 72 in 150 seconds
INFO: worker Thread-15 finished device 169 in 153 seconds
INFO: worker Thread-19 finished device 47 in 131 seconds
INFO: worker Thread-11 finished device 84 in 100 seconds
INFO: worker Thread-21 finished device 109 in 98 seconds
INFO: worker Thread-13 finished device 164 in 106 seconds
INFO: worker Thread-14 finished device 61 in 70 seconds
INFO: worker Thread-8 finished device 55 in 97 seconds
INFO: worker Thread-17 finished device 133 in 108 seconds
INFO: worker Thread-9 finished device 101 in 112 seconds
INFO: worker Thread-6 finished device 118 in 100 seconds
WARNING: worker Thread-4 finished device 6 in 486 seconds
INFO: worker Thread-22 finished device 16 in 75 seconds
INFO: worker Thread-5 finished device 150 in 166 seconds
INFO: worker Thread-23 finished device 32 in 23 seconds
INFO: worker Thread-12 finished device 48 in 53 seconds
INFO: worker Thread-16 finished device 46 in 21 seconds
INFO: worker Thread-20 finished device 62 in 28 seconds
INFO: worker Thread-15 finished device 34 in 22 seconds
INFO: worker Thread-19 finished device 78 in 19 seconds
INFO: worker Thread-7 finished device 12 in 196 seconds
INFO: worker Thread-8 finished device 67 in 35 seconds
INFO: worker Thread-9 finished device 64 in 39 seconds
INFO: worker Thread-11 finished device 92 in 45 seconds
INFO: worker Thread-6 finished device 140 in 48 seconds
INFO: worker Thread-10 finished device 22 in 65 seconds
INFO: worker Thread-21 finished device 56 in 49 seconds
INFO: worker Thread-22 finished device 89 in 50 seconds
INFO: worker Thread-14 finished device 143 in 54 seconds
INFO: worker Thread-12 finished device 31 in 49 seconds
INFO: worker Thread-4 finished device 40 in 58 seconds
INFO: worker Thread-5 finished device 88 in 63 seconds
INFO: worker Thread-19 finished device 123 in 64 seconds
INFO: worker Thread-23 finished device 170 in 72 seconds
INFO: worker Thread-17 finished device 155 in 79 seconds
INFO: worker Thread-15 finished device 135 in 79 seconds
INFO: worker Thread-20 finished device 24 in 82 seconds
INFO: worker Thread-16 finished device 141 in 84 seconds
INFO: worker Thread-8 finished device 105 in 56 seconds
INFO: worker Thread-9 finished device 173 in 54 seconds
INFO: worker Thread-18 finished device 184 in 267 seconds
INFO: worker Thread-13 finished device 41 in 97 seconds
INFO: worker Thread-22 finished device 39 in 47 seconds
WARNING: worker Thread-3 finished device 13 in 583 seconds
INFO: worker Thread-4 finished device 23 in 39 seconds
INFO: worker Thread-11 finished device 79 in 64 seconds
INFO: worker Thread-5 finished device 11 in 41 seconds
INFO: worker Thread-19 finished device 49 in 30 seconds
INFO: worker Thread-6 finished device 38 in 56 seconds
INFO: worker Thread-14 finished device 54 in 51 seconds
INFO: worker Thread-16 finished device 58 in 14 seconds
INFO: worker Thread-10 finished device 35 in 56 seconds
INFO: worker Thread-7 finished device 43 in 91 seconds
INFO: worker Thread-21 finished device 100 in 59 seconds
INFO: worker Thread-12 finished device 110 in 53 seconds
INFO: worker Thread-23 finished device 111 in 32 seconds
INFO: worker Thread-20 finished device 97 in 19 seconds
INFO: worker Thread-22 finished device 91 in 11 seconds
INFO: worker Thread-8 finished device 121 in 18 seconds
INFO: worker Thread-18 finished device 82 in 15 seconds
INFO: worker Thread-3 finished device 86 in 15 seconds
INFO: worker Thread-17 finished device 99 in 36 seconds
INFO: worker Thread-13 finished device 115 in 19 seconds
INFO: worker Thread-9 finished device 36 in 22 seconds
INFO: worker Thread-16 finished device 175 in 13 seconds
INFO: worker Thread-6 finished device 178 in 17 seconds
INFO: worker Thread-11 finished device 80 in 19 seconds
INFO: worker Thread-15 finished device 163 in 34 seconds
INFO: worker Thread-4 finished device 63 in 25 seconds
INFO: worker Thread-14 finished device 137 in 19 seconds
INFO: worker Thread-7 finished device 27 in 18 seconds
INFO: worker Thread-21 finished device 51 in 16 seconds
INFO: worker Thread-19 finished device 117 in 19 seconds
INFO: worker Thread-5 finished device 29 in 19 seconds
INFO: worker Thread-12 finished device 102 in 16 seconds
INFO: worker Thread-10 finished device 83 in 19 seconds
INFO: worker Thread-23 finished device 144 in 16 seconds
INFO: worker Thread-20 finished device 94 in 16 seconds
INFO: worker Thread-22 finished device 60 in 40 seconds
INFO: worker Thread-3 finished device 119 in 36 seconds
INFO: worker Thread-8 finished device 125 in 43 seconds
INFO: worker Thread-13 finished device 33 in 45 seconds
INFO: worker Thread-17 finished device 108 in 55 seconds
INFO: worker Thread-18 finished device 145 in 62 seconds
INFO: worker Thread-12 finished device 136 in 59 seconds
INFO: worker Thread-19 finished device 116 in 69 seconds
INFO: worker Thread-16 finished device 129 in 75 seconds
INFO: worker Thread-4 finished device 59 in 72 seconds
INFO: worker Thread-11 finished device 103 in 72 seconds
INFO: worker Thread-9 finished device 114 in 88 seconds
INFO: worker Thread-6 finished device 134 in 123 seconds
INFO: worker Thread-14 finished device 106 in 133 seconds
INFO: worker Thread-10 finished device 104 in 140 seconds
INFO: worker Thread-15 finished device 77 in 141 seconds
INFO: worker Thread-21 finished device 26 in 142 seconds
INFO: worker Thread-5 finished device 87 in 142 seconds
INFO: worker Thread-7 finished device 85 in 142 seconds
INFO: worker Thread-23 finished device 14 in 145 seconds
INFO: worker Thread-20 finished device 81 in 148 seconds
INFO: worker Thread-8 finished device 15 in 123 seconds
INFO: worker Thread-13 finished device 174 in 115 seconds
INFO: worker Thread-17 finished device 17 in 105 seconds
INFO: worker Thread-22 finished device 4 in 128 seconds
INFO: worker Thread-3 finished device 74 in 127 seconds
WARNING: worker Thread-2 finished device 165 in 881 seconds
WARNING: worker Thread-1 finished device 166 in 940 seconds
INFO: poller-wrapper polled 161 devices in 940 seconds with 23 workers
WARNING: the process took more than 300 seconds to finish, you need faster hardware or more threads
INFO: in sequential style polling the elapsed time would have been: 17051 seconds
WARNING: device 6 is taking too long: 486 seconds
WARNING: device 13 is taking too long: 583 seconds
WARNING: device 18 is taking too long: 310 seconds
WARNING: device 138 is taking too long: 319 seconds
WARNING: device 149 is taking too long: 306 seconds
WARNING: device 165 is taking too long: 881 seconds
WARNING: device 166 is taking too long: 940 seconds
WARNING: device 167 is taking too long: 302 seconds
ERROR: Some devices are taking more than 300 seconds, the script cannot recommend you what to do.

Looks like you need to figure out why it takes so long to poll devices 165 and 166.

https://docs.librenms.org/#Support/FAQ/#why-do-i-see-gaps-in-my-graphs

@murrant Thanks for yout prompt reply.

These are Cisco 5520 Wireless Controllers. Once again, this started after the Librenms update early this morning. Was something pushed that had to do with these devices?

The controllers are working as expected and do not have any issues.

-Mike

Longer than 300s polling is not working properly.

Perhaps run the poller.php by hand for one device and check the output.
Also, did you look at the graphs mentioned in the docs I linked?