FS#40177 - [dhclient] Corrupt lease file - possible data loss!

Attached to Project: Arch Linux
Opened by Robert Orzanna (orschiro) - Thursday, 01 May 2014, 20:32 GMT
Last edited by Anatol Pomozov (anatolik) - Sunday, 11 May 2014, 18:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Isenmann Daniel (ise)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I get the following warning on resume from hibernation:

Mai 01 22:19:29 thinkpad dhclient[23692]: Corrupt lease file - possible data loss!
Mai 01 22:19:29 thinkpad dhclient[23692]: Corrupt lease file - possible data loss!
Mai 01 22:19:29 thinkpad dhclient[23692]: Corrupt lease file - possible data loss!
Mai 01 22:19:29 thinkpad dhclient[23692]: Corrupt lease file - possible data loss!
Mai 01 22:19:29 thinkpad dhclient[23692]: Corrupt lease file - possible data loss!

Additional info:

netctl 1.6-1
dhclient 4.3.0-1
wpa_supplicant 2.1-3

Steps to reproduce:

I use a laptop and usually do the following:

1. Connect to a wifi network.
2. Put laptop into hibernation and move to a different physical location with a different wifi network
3. Resume from hibernation.
4. Netctl will use dhclient to automatically connect to the different wifi network
5. dhclient throws out the error warning above

Why does my lease file get corrupt?

Thanks!
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Sunday, 11 May 2014, 18:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed upstream
Comment by Anatol Pomozov (anatolik) - Thursday, 01 May 2014, 22:19 GMT
This sounds like an upstream issue. Please contact the project maillist instead.
Comment by Robert Orzanna (orschiro) - Friday, 02 May 2014, 06:03 GMT
Thank you. Following your advice I posted this issue to dhcp-bugs@isc.org.

Any further comments are welcome.

Let me please know if I can provide you with additional information.
Comment by Robert Orzanna (orschiro) - Sunday, 11 May 2014, 17:08 GMT
Issue has been fixed thanks to upstream.

Loading...