-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
[bug] Persistent notification - Cause: Integer name casues backend restart #874
Comments
Thank you for your answer! My logs folder is more than 200MB can I upload he folder through a google drive link? |
Sure, even better if you only share the part of your logs with the exception, just before the backend restarted. You might need to check Portainer to get these exceptions. See these guides for additional details: https://github.com/jokob-sk/NetAlertX/blob/main/docs/DEBUG_PLUGINS.md https://github.com/jokob-sk/NetAlertX/blob/main/docs/DEBUG_TIPS.md |
Thank you very much, I've sent the log to your email address if they are too big as soon as I come back tonight I'll try to locate the important part and paste it here |
Haven't received anything so far. |
I've sent the log with my gmail to the mail reported on the previous links |
It was in the spam folder. Regrettably however the log files are inconclusive. As mentioned above, sometimes the only way to catch an exception is in the docker/portainer logs. Can you please share any exceptions logged in there before the backend restarts:
usually an exception can be found before these lines of log output. |
is this part?
|
Thank you @sk8er000 , This is exactly what I needed. This should be fixed in the next release. It would be great if you could test this. Can you please switch to the Make sure you refresh your browser cache - and click the 🔄 refresh button in the top right corner. Thanks in advance, |
I'm sorry for the late reply, at the moment I can't easily access to my docker installation but I can try as soon as I can. Some hours at worse |
no rush @sk8er000 - thanks for the help 🙏 |
Sorry for the delay but I came back at night and went to sleep. I've redeployed my container using the dev branch. When I logged to the web I terface I received the same notification but after doing all the reported steps it disappeared and now I can use the web interface! I'll try more deeply today and report here. In the meanwhile thank you very much for the prompt fix! |
No need to apologize and thanks for testing! |
It's now a couple of days and didn't notice any issue with the actual dev branch image, I think that my issue is completely fixed. Thank you! 🍻 |
Hi @sk8er000 - glad to hear that and thanks for testing! |
Releasing -> Closing |
Is there an existing issue for this?
The issue occurs in the following browsers. Select at least 2.
Current Behavior
Opening the web interface from the browser it appears the following notification:
[Upgrade] : App upgraded 🚀 Please clear the cache:
Check out new features and what has changed in the 📓 release notes.
But after doing every step multiple times the notification still pops up.
Expected Behavior
The notification should disappear after doing all the steps
Steps To Reproduce
No response
app.conf
No response
docker-compose.yml
No response
What branch are you running?
Production
app.log
No response
Debug enabled
The text was updated successfully, but these errors were encountered: