-
Notifications
You must be signed in to change notification settings - Fork 490
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
panic: runtime error: invalid memory address or nil pointer dereference when running a replay when tick script contains post() #1547
Comments
After commenting out '.post()' it works fine, so the issue is with '.post()'. At a closer inspection I realised I have:
with single quotes, when the docs here: https://docs.influxdata.com/kapacitor/v1.3/nodes/alert_node/ indicate that I should use double quotes, but with double quotes:
So I changed it to use 'endpoint()' and single quotes:
but when I attempted to replay it - container died again in exactly the same way. |
I have just run into this as well, using the latest docker image I found that having I have ended up having to use the 1.2.1 container where the problem doesn't exist. I found the same issue with the 1.3 container. |
@pshemk @MarcDenman Just to clarify, the panic only occurs when using a replay, or does it also occur when using the task is running? |
@desa I only tried using a replay, for some reason I didn't even think about actually running the task and seeing if it happened "normally", sorry! |
@MarcDenman no problem, I'm sorry that it's panicking in the first place. It definitely shouldn't do that. |
|
Awesome! Thanks. I've got a PR open with a fix. Just need to add some tests and then it should be good to go. |
Hi,
I was following instructions on https://docs.influxdata.com/kapacitor/v1.3/introduction/getting_started/
Kapacitor is running in a container from the official image tagged :latest
Tick script i tried to use:
I recorded the stream:
But when I tried to replay it:
root@kapacitor:/var/lib/kapacitor# kapacitor replay -recording $rid -task load_alert
container crashed:
The text was updated successfully, but these errors were encountered: