-
-
Notifications
You must be signed in to change notification settings - Fork 311
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
portmaster freezes on gentoo after changing time #1349
Comments
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
|
figured out it works as intended if only I wait. so set clock forward by 1 hour and then wait for 1 hour and it'll work again. here's the debug info once that happened (clock got changed by gentoo backwards from 12:19 to 11:19 and it started working at 12:19): Version 1.5.1
Platform: gentoo 2.14
Compat Module Error
Unexpected Logs
Status: Trusted
SPN: disabled (module disabled)
Resolvers: 4/4
Config: 5
Updates: stable (13/27)
Compatibility: IPTables Chains (36)
Goroutine Stack
|
Thanks for letting us know |
what happens is I start my computer and have all my internet blocked by portmaster and an empty black window titled portmaster is visible. then I restart the computer and everything works as expected.
what I expect to happen is that it works without the need to restart. what eventually allowed me to work without reboot is to
systemctl stop portmaster
i.e. turn off my firewall and internet is accessible again. I expect this not to be necessary and must mention that issuing this command on a console will never exit ultil I press ctrl-c. similarily when rebooting the portmaster service needs to time-out for reboot to happen...
to reproduce the bug try setting date-time forward by 2 hours in bios before booting into a systemd linux with portmaster installed and some time-server. during startup of portmaster time gets changed back and the freeze will happen. race-condition? after the system has set the clock correctly, booting again will work correctly again...
sorry, no debug info, no idea how to get it without an actual interface...
The text was updated successfully, but these errors were encountered: