We've received an image of the SD card of the affected raspberry Pi and could not reproduce this issue after a week of "aging" where the device was left idle, connected to the network, and operating normally at all times.
I cannot explain the failure that was originally seen by Roger. I suspect it is something environmental, specific to the hardware used.
We can perform further debugging to try to pinpoint the cause but I don't believe it is a specific issue in the software in general but instead an intersection of the software and particular hardware that we were unable to reproduce elsewhere.
I've un-assigned myself from the issue to reflect the current status.
We've received an image of the SD card of the affected raspberry Pi and could not reproduce this issue after a week of "aging" where the device was left idle, connected to the network, and operating normally at all times.
I cannot explain the failure that was originally seen by Roger. I suspect it is something environmental, specific to the hardware used.
We can perform further debugging to try to pinpoint the cause but I don't believe it is a specific issue in the software in general but instead an intersection of the software and particular hardware that we were unable to reproduce elsewhere.
I've un-assigned myself from the issue to reflect the current status.