App fails to find mysterious "uptime" field in DHCP lease info #291

Open
opened 2026-02-20 08:21:46 -05:00 by deekerman · 1 comment
Owner

Originally created by @dseven on GitHub (May 25, 2025).

Originally assigned to: @ym on GitHub.

Noticed that my display was waking up for no apparent reason, and linked it to this event every hour:

2025-05-25T10:32:54Z INF jetkvm timesync syncing system time
2025-05-25T10:32:54Z INF jetkvm timesync HTTP server returned time http_url=http://www.gstatic.com/generate_204 request_id= status=204 time_taken=56.494381ms
2025-05-25T10:32:54Z INF jetkvm timesync set rtc time offset=0s rtc_time=2025-05-25T10:32:54Z
2025-05-25T10:32:54Z INF jetkvm timesync time sync successful now=2025-05-25T10:32:54Z time_taken=66.546673ms
2025-05-25T10:32:55Z ERR jetkvm network failed to get dhcp lease expiry error="uptime or lease time isn't set" interface=eth0
2025-05-25T10:32:55Z INF jetkvm display set brightness brightness=64

The code appears to be looking for a field named uptime in the udhcp lease info file, but there is no such field - neither in the file on my device nor in the documentation. I wonder where the author was expecting this field to come from - perhaps a customisation to udhcpc that has not yet been rolled out??

Originally created by @dseven on GitHub (May 25, 2025). Originally assigned to: @ym on GitHub. Noticed that my display was waking up for no apparent reason, and linked it to this event every hour: ``` 2025-05-25T10:32:54Z INF jetkvm timesync syncing system time 2025-05-25T10:32:54Z INF jetkvm timesync HTTP server returned time http_url=http://www.gstatic.com/generate_204 request_id= status=204 time_taken=56.494381ms 2025-05-25T10:32:54Z INF jetkvm timesync set rtc time offset=0s rtc_time=2025-05-25T10:32:54Z 2025-05-25T10:32:54Z INF jetkvm timesync time sync successful now=2025-05-25T10:32:54Z time_taken=66.546673ms 2025-05-25T10:32:55Z ERR jetkvm network failed to get dhcp lease expiry error="uptime or lease time isn't set" interface=eth0 2025-05-25T10:32:55Z INF jetkvm display set brightness brightness=64 ``` [The code](https://github.com/jetkvm/kvm/blob/a28676cd94d64aad156dee7c7ba779acdca0d3ec/internal/udhcpc/parser.go#L46) appears to be looking for a field named `uptime` in the udhcp lease info file, but there is no such field - neither in the file on my device nor in [the documentation](https://udhcp.busybox.net/README.udhcpc). I wonder where the author was expecting this field to come from - perhaps a customisation to udhcpc that has not yet been rolled out??
Author
Owner

@dseven commented on GitHub (Jun 5, 2025):

Symptoms (error message and display waking up) appear to have gone away with the latest dev code, presumably due to #540 . Still curious about this "uptime" field, though...

@dseven commented on GitHub (Jun 5, 2025): Symptoms (error message and display waking up) appear to have gone away with the latest dev code, presumably due to #540 . Still curious about this "uptime" field, though...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/kvm#291
No description provided.