-
Notifications
You must be signed in to change notification settings - Fork 21
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
WinNUT v2.0.7722.30975 Always stays disconnected after suspend/resume cycle. #4
Comments
Thank you for reporting this. Can you try the pre-release version? I thought this bug was only in 2.1, but I'd just like to be sure. For tracking purposes, I think this is related to: |
So I updated to 2.1.7740.35837.... Last available version that I can find an installer... Let me see if any problem crops up... |
I'm working on a fairly big update in #11 right now. Feel free to follow my progress there, and I'll upload a debug build if you wouldn't mind testing later. If it doesn't fix this issue, then it should at least narrow down what's causing it. |
Improve Connection handling & Logging, Power State handling
Hey, sorry for answering late... I think it works better, at least you worked out the startup hangs |
Hi, on lastest version "remaining time:" is totally broken.... UPS config: |
No worries, thank you for getting back to me. Would you please test a suspend/resume cycle and let me know of the results? If successful, I think we should close this issue as resolved. If you wouldn't mind, I'd appreciate it if you opened a new ticket for the remaining time being blank. I know it's been reported on gawindx's repository before and I'd like to investigate why the remaining time calculation was disabled. |
Reconnect after suspend/resume is still not working for me on version 2.2.8255.34401. I have to manually reconnect using Connection > Reconnect. |
Could you please provide a debug log including when the computer resumes, and about 30 seconds after? |
Hi, gbakeman I had to create a bug report because WinNUT is not behaving properly |
Was there an issue creating the report? When you go to make it, it will open a folder where the report is located. You can then drag the report file into the comment response below to upload it. Thank you for reporting! |
FWIW, I'm seeing this on 2.2.8303.20598. |
Everyone, I believe this issue has been fully fixed as of pre-release v2.2.8328. Please update or download the latest version from the releases and report back if this issue persists. |
I updated to 2.2.8328 last night and it reconnected on its own this morning. Thanks gbakeman :) |
You're welcome, thank you for letting me know! |
Hi, I´m running WinNUT on my Surface Pro3 this is connected to a CDP UPS (monitored by NUT on OpenWRT), everything works wonderfully.
Because this is my main machine I do suspend/resume cycle various times a day, WinNUT sometimes comes back with a Max retries reached and doesn't retry connecting.
The same things happens if one of my Wi-Fi mesh AP's goes down for long enough (time to hop to next AP), it disconnects uses all retries and ends up disconnected.
Even if my network and NUT server are still up.
Could you please add code to check network status change and retry reconnection if network get disconnected / reconnected, or power status (coming out of hibernation) changes, by tracking said network status.
The text was updated successfully, but these errors were encountered: