-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Service terminates (no info)? #3217
Comments
Is there an ability to increase verbosity for the logging? I've search the project and have not found any indication that its possible. |
Couldn't find verbose logging either, but this might be an external cause, ie. something sending the process a SIGTERM. |
Yeah good idea. I started looking for other applications and found that a docker instance of file browser I hadn't terminated correctly was running. Stopped that container and it no termination issues with the service since. |
Description
I'm running filebrowser as a service with systemd (on Ubuntu 22). It runs fine, but over the past few days its terminates and I have no insight due to lack of verbosity in logging. Any ideas on determining if its a issue with filebrowser or my host? With no error from filebrowser besides below its making it pretty tricky.
Below is the only log data that indicates an issue from the filebrowser side.
This has happen twice now since installing it. I set this up over the weekend.
Here is my config for filebrowser.
And the config for the service:
The text was updated successfully, but these errors were encountered: