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

Uncaught Lua error: bad argument #1 #17

Open
GrandFelix opened this issue Oct 26, 2022 · 2 comments
Open

Uncaught Lua error: bad argument #1 #17

GrandFelix opened this issue Oct 26, 2022 · 2 comments

Comments

@GrandFelix
Copy link

Hi,

on one of our servers we get next error PANIC: Uncaught Lua error: bad argument #1 to '?' (datum), it is very randomly and we cant reproduce it. Is there any option that we get more info in postgres logs so we can see where is the problem (line number etc.)? Is there any pllua config or something?

Thanks

@RhodiumToad
Copy link
Owner

Sorry for the delayed response. That error shouldn't ever happen; the best way to diagnose it will be to get the stack trace (any PANIC error will result in a core dump if you enable those). Are you using the untrusted language and loading any modules?

@GrandFelix
Copy link
Author

Hi. I did miss this comment. Sorry. No, we are not using untrusted lang. We only load one module local jsonb = require "pllua.jsonb"; Ok, I will check if we have enabled core dumps for PANIC errors on servers, if not, we will enable it and I will come back.

Thanks for your reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants