Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MonitorConfigPoller panic: runtime error: invalid memory address or nil pointer dereference #2250

Closed
smalenfant opened this issue May 10, 2018 · 4 comments
Labels
bug something isn't working as intended Traffic Monitor related to Traffic Monitor

Comments

@smalenfant
Copy link
Contributor

Traffic Monitor crash and exited. I don't have much details except that procNetDev was not returning from astats json output.

From traffic_monitor.log:

ERROR: cache.go:325: 2018-04-16T17:08:34.339643848Z: precomputeAstats psp6cdedge03 handle precomputing outbytes 'procNetDev empty'
ERROR: stat.go:87: 2018-04-16T17:08:34.351132976Z: stat poll getting vitals for psp6cdedge03: Error parsing procnetdev: no fields found
ERROR: cache.go:325: 2018-04-16T17:08:42.098836427Z: precomputeAstats psp6cdedge03 handle precomputing outbytes 'procNetDev empty'
ERROR: stat.go:87: 2018-04-16T17:08:42.10609049Z: stat poll getting vitals for psp6cdedge03: Error parsing procnetdev: no fields found
ERROR: asm_amd64.s:2197: 2018-04-18T01:31:26.283370864Z: MonitorConfigPoller: getting monitor config map: Get https://cdn1cdcms0001.coxlab.net/api/1.2/cdns/cdn1/configs/monitoring.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
 <nil>
ERROR: asm_amd64.s:514: 2018-04-28T05:30:01.733534769Z: MonitorConfigPoller panic: runtime error: invalid memory address or nil pointer dereference
@smalenfant smalenfant added bug something isn't working as intended Traffic Monitor related to Traffic Monitor labels May 10, 2018
@rob05c
Copy link
Member

rob05c commented May 10, 2018

We've seen this before, but very rarely, and only in the lab.

This was added, to dump the stacktrace when it happens, to tell us where it is:
#1894
8227159

But we haven't seen it since that was added. If possible, can you apply that changeset? If you can get it to panic with that changeset, it should tell us where the panic is so we can fix it.

@mitchell852
Copy link
Member

@smalenfant ^^

@rob05c
Copy link
Member

rob05c commented Jul 20, 2018

Hopefully fixed by #2377 but confirmation would be good.

@rob05c
Copy link
Member

rob05c commented Sep 18, 2018

I'm closing this, assuming #2377 fixed. Feel free to reopen if you see this issue again.

@rob05c rob05c closed this as completed Sep 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended Traffic Monitor related to Traffic Monitor
Projects
None yet
Development

No branches or pull requests

3 participants