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

PANIC: unprotected error in call to Lua API (bad light userdata pointer) #199

Closed
MadDoct opened this issue Apr 17, 2019 · 23 comments
Closed

Comments

@MadDoct
Copy link

MadDoct commented Apr 17, 2019

Problem/Motivation

Node-Red doesn't start in the new version - worked before...

(Why the issue was filed)

Expected behavior

It should start as normal

(What you expected to happen)

Actual behavior

It stops with the following error:
[09:22:40] INFO: Starting NGinx...
17 Apr 09:22:40 - [info] Starting flows
17 Apr 09:22:40 - [info] Started flows
PANIC: unprotected error in call to Lua API (bad light userdata pointer)

(What actually happened)

Steps to reproduce

Starting the add-on

(How can someone else make/see it happen)

Proposed changes

Update nginx to a version that supports aarch64...

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

@deece

This comment has been minimized.

@deece
Copy link

deece commented Apr 18, 2019

Broken in 4f3d08b

The LUA module requires a patch (already in mainline), so it will have to be built from source until the Alpine packages catch up: openresty/lua-nginx-module#1379

@frenck
Copy link
Member

frenck commented Apr 18, 2019

This is an upstream issue with Alpine.
I know the module has issues on aarch64/ARMv8/64bits ARM devices. It has been fixed in the openresty mainline in Oct 2018 and released in Feb 2019. Nevertheless, Alpine has not updated.

For the record, I'm not going to compile this in manually, because it requires more than simply compiling a module.

Please note: on the Home Assistant documentation, the 32 bits version is still recommended.

@deece
Copy link

deece commented Apr 18, 2019

Can you please advise how to roll back to an older version of the addon?

@frenck
Copy link
Member

frenck commented Apr 18, 2019

Hassio currently provides no way to do that.

@deece
Copy link

deece commented Apr 18, 2019

I'm logging this with Alpine, but in the meantime, could you please disable this feature on aarch64 so those of us who use it can get control of our house again?

@frenck
Copy link
Member

frenck commented Apr 18, 2019

I'm currently building a PR for the Alpine aport repository.

No I can't disable this for aarch64.

@deece
Copy link

deece commented Apr 18, 2019

@frenck
Copy link
Member

frenck commented Apr 18, 2019

Your upstream bug report is incorrect, but thanks.

@deece
Copy link

deece commented Apr 18, 2019

Dupe of #193

@frenck
Copy link
Member

frenck commented Apr 18, 2019

@deece

alpinelinux/aports#7121
alpinelinux/aports#7122

@deece
Copy link

deece commented Apr 18, 2019

Awesome, thankyou :)

@frenck
Copy link
Member

frenck commented May 7, 2019

Upstream has been fixed (Alpine) and even backported to Alpine 3.9.
The development branch Node-RED has been updated, will be fixed in the next add-on release.

@charlietomo
Copy link

@frenck do you have an estimate of when the next release will be? Thanks

@frenck
Copy link
Member

frenck commented May 11, 2019

I don't work on a schedule.

@charlietomo
Copy link

I don't work on a schedule.

Understood, but an estimate of time quantum (days/weeks/months) would help those of us who rely on Node-Red to make a decision on the way forward. I've just moved from RaspberryPi to Odroid C2 and (unintentionally) moved from 32 to 64bit, which is causing a bunch of problems with add-ons related to unprotected error in call to Lua API. If this is a long term problem I will spin up Node Red elsewhere in order to get my setup working again - but that is a sub optimal solution.

I am making the assumption there is nothing I as a non programmer can do to help expedite this; if there is, please say.

@frenck
Copy link
Member

frenck commented May 18, 2019

@charlietomo Several months.

@frenck
Copy link
Member

frenck commented May 18, 2019

Fixed in release v3.1.0

@frenck frenck closed this as completed May 18, 2019
@agoralive
Copy link

When will this be available in the hass.io? I still only see v3.0.3

@frenck
Copy link
Member

frenck commented May 18, 2019

@agoralive It is already there.
Maybe your Hass.io instance didn't pick it up yet (can take up to 8 hours).
You can force it, by going into the Hass.io panel -> Add-on store -> Click the refresh icon in the top right.

@sinclairpaul
Copy link
Member

Refresh the addon store (top right corner), it is available now.

@charlietomo
Copy link

Thanks for the update, this now runs on my Odroid C1.

@addons-assistant
Copy link

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@addons-assistant addons-assistant bot locked as resolved and limited conversation to collaborators Jun 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants