Skip to content
This repository has been archived by the owner on Apr 22, 2019. It is now read-only.

Panic related to Lua API #24

Open
f-izzo opened this issue Oct 21, 2018 · 2 comments
Open

Panic related to Lua API #24

f-izzo opened this issue Oct 21, 2018 · 2 comments
Labels
upstream For issues dependent on upstream resolution

Comments

@f-izzo
Copy link

f-izzo commented Oct 21, 2018

After obtaining the certificates, the container loops with the following error:

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

I'm running Arch Linux ARM on a NanoPi Neo 2, a single board computer with an Allwinner H5 armv8 cpu.

The container is being run by user fede through docker-compose

Full docker log output:

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1001
User gid:    1002
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing... 
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing... 
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing... 
Variables set:
PUID=1001
PGID=1002
TZ=Europe/Rome
URL=xxxxx
SUBDOMAINS=xxx
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
DHLEVEL=2048
VALIDATION=
DNSPLUGIN=
EMAIL=xxxxxx
STAGING=

VALIDATION parameter not set; setting it to http
2048 bit DH parameters present
SUBDOMAINS entered, processing
SUBDOMAINS entered, processing
Sub-domains processed are:  -d xxxxx
E-mail address entered: xxxxxx
http validation is selected
Certificate exists; parameters unchanged; attempting renewal
<------------------------------------------------->

<------------------------------------------------->
cronjob running on Sun Oct 21 22:23:56 CEST 2018
Running certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/izzo.pro.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert not yet due for renewal

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The following certs are not due for renewal yet:
  /etc/letsencrypt/live/xxxxx/fullchain.pem expires on 2019-01-19 (skipped)
No renewals were attempted.
No hooks were run.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[cont-init.d] 50-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
Server ready
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)

@XtracT
Copy link

XtracT commented Oct 23, 2018

Hi,

I could solve it by removing these two files inside the container (I removed them and made a new image) :
/etc/nginx/modules/http_lua.conf
/etc/nginx/modules/http_lua_upstream.conf

However,

I have also found this:
openresty/lua-nginx-module#1379

So I guess the good approach would be to use the latest lua-nginx-module.

/Xtract

@aptalca
Copy link
Member

aptalca commented Oct 23, 2018

Thanks for linking to that issue. It is indeed an upstream issue. Now we just have to wait until the module package is updated on alpine

@homerr homerr added the upstream For issues dependent on upstream resolution label Nov 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream For issues dependent on upstream resolution
Projects
None yet
Development

No branches or pull requests

4 participants