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

Syncthing panic not shown on GUI #7070

Open
Xeenych opened this issue Oct 30, 2020 · 2 comments
Open

Syncthing panic not shown on GUI #7070

Xeenych opened this issue Oct 30, 2020 · 2 comments
Labels
enhancement New features or improvements of some kind, as opposed to a problem (bug)

Comments

@Xeenych
Copy link

Xeenych commented Oct 30, 2020

I have ST running on my laptop. I was trying to sync for a whole day unsuccessfuly. Then I looked at console window and saw panic messages due to corrupt database.
So, what is happening.

ST starts -> tries to sync -> panic -> ST restarts -> tries to sync -> panic - and so on.

There is no indication on GUI, but there should be!

If ST runs as a service without any console windows, the user cannot find if the panic happens

@Xeenych Xeenych added enhancement New features or improvements of some kind, as opposed to a problem (bug) needs-triage New issues needed to be validated labels Oct 30, 2020
@imsodin
Copy link
Member

imsodin commented Oct 30, 2020

That's not possible for persistent panics: A panic brings the entire program down, i.e. there is no web UI in which to display the panic. It should however be obvious that something is wrong when trying to open the UI, because it's either not there or keeps dis- and reappearing.
For one off panics, i.e. if it doesn't occur anymore thus the UI can run, it would indeed make sense to detect the previous panics and show an indication in the web UI.

@imsodin imsodin removed the needs-triage New issues needed to be validated label Oct 30, 2020
@Xeenych
Copy link
Author

Xeenych commented Oct 30, 2020

In my case panic occured every ~5-10 min. So, every 5-10 minutes I saw a disconenct in web-interface and then immediate reconnect. It looked as a normal behaviour.
So detecting prevoous panics would be very helpful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New features or improvements of some kind, as opposed to a problem (bug)
Projects
None yet
Development

No branches or pull requests

2 participants