Replies: 2 comments 3 replies
-
|
I've just updated and noticed some strange behaviour under Windows 10. The web interface is timing out, but there aren't any errors in the log, I'm just seeing: If I exit System Bridge from the tray icon, it appears to close successfully. However, each time I re-launch, the closed instance(s) seem to reopen in addition to one new instance. e.g. closing and reopening the first time results in two System Bridge tray icons, the second time results in three icons, etc. There are some errors corresponding to these events: Full logs here. I started with an in-place update from 2.5.0 to 2.6.0, and when these issues came up, I uninstalled, deleted the Program Files and App Data folders (it seemed like the NodeJS runtime kept running and prevented clean uninstallation), rebooted and installed again. This didn't seem to make any difference. The MQTT service still seems to work, but not the API endpoints (unsure if this is for the same reason the web interface isn't working, or because I'm missing the regenerated api key) |
Beta Was this translation helpful? Give feedback.
-
|
Same behaviour here, can't access settings or view data anymore. |
Beta Was this translation helpful? Give feedback.
-
|
Nothing looks out of order from the logs there from what I can see. Can you open the path the app is installed to where you can see both executables and the additional files:
From there, open this folder in a terminal/powershell and manually run the app from there:
You should then see the log output show. This may give some additional information that is not handled by the logger module |
Beta Was this translation helpful? Give feedback.
-
|
Still happens in 2.7.2 (and version shows as 2.7.1) as below: 2021-09-26 13:39:23 info: System Bridge 2.7.1: C:\Users\spitz66\AppData\Local\System Bridge - C:\Users\spitz66\AppData\Local\System Bridge\system-bridge.exe - C:\Users\spitz66\AppData\Local\System Bridge - ["C:\Users\spitz66\AppData\Local\System Bridge\system-bridge.exe","C:\snapshot\system-bridge\dist\index.js"] - - - - When reverting to 2.5.0 everything works again except for CPU load issue. |
Beta Was this translation helpful? Give feedback.
-
|
When I try running via CMD, it does give some error but closes the window a split second later so I haven't been able to capture what it says. The same behaviour is happening for me on 2.7.3, but I'm not sure if the error might be related to the process being re-launched automatically and conflicting with the cmd process |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What’s changed
✨ New features
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
This discussion was created from the release v2.6.0.
Beta Was this translation helpful? Give feedback.
All reactions