-
Notifications
You must be signed in to change notification settings - Fork 293
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
Exit status 130 #574
Comments
Hi there! I actually have no idea what's up with an exit code 130 – I've not seen it before – but the logs complain about unsafe permissions and not being able to execute the start script. Maybe try reinstalling it? Additionally, it looks like you're on 2.8.1 (outdated). Please upgrade to 2.9.0 and try again! I've seen the Let me know how it goes |
130 is a (user) abort exit code. even tells you |
I now updated it, I don't know if I will be able to directly see the error somewhere or so, but yeah we will see how it goes |
is my error, how to fix? It did worked before?
ps. in the real logs i can see it spams with
p.s. this is on an openbsd vps
The text was updated successfully, but these errors were encountered: