seanleblanc
Cadet
- Joined
- Jun 13, 2022
- Messages
- 2
I'm now running TrueNAS-12.0-U8.1, but even on FreeNAS, I've had this issue that would crop up from time to time - the machine would become unresponsive - ping, web interface, and NFS would all be non-responsive. Trying to plugin the HDMI cable into a monitor and use the keyboard would not seem to get the computer to wake up, either - I would have to power cycle the machine.
However, what I've noticed is that the interface I've used had DHCP clicked on it, and so it was getting a secondary IP besides a static one I set. The last thing I saw in /var/log/messages before the machine was power cycled seem to be related to the interface going up and down:
I've turned off DHCP for this interface now. Do you think it's possible that turning on DHCP for this interface was possibly causing the network to stop responding at later times like this? If not, is there extra debugging I can turn on to try to troubleshoot this problem?
However, what I've noticed is that the interface I've used had DHCP clicked on it, and so it was getting a secondary IP besides a static one I set. The last thing I saw in /var/log/messages before the machine was power cycled seem to be related to the interface going up and down:
Jun 13 16:32:31 freenas kernel: re0: link state changed to DOWN
Jun 13 16:32:34 freenas 1 2022-06-13T16:32:34.577984-06:00 freenas.local dhclient 7685 - - New IP Address (re0): 192.168.0.178
Jun 13 16:32:34 freenas 1 2022-06-13T16:32:34.579096-06:00 freenas.local dhclient 7686 - - New Subnet Mask (re0): 255.255.255.0
Jun 13 16:32:34 freenas 1 2022-06-13T16:32:34.580215-06:00 freenas.local dhclient 7687 - - New Broadcast Address (re0): 192.168.0.255
Jun 13 16:32:34 freenas 1 2022-06-13T16:32:34.581317-06:00 freenas.local dhclient 7688 - - New Routers (re0): 192.168.0.1
Jun 13 16:32:34 freenas kernel: re0: link state changed to UP
Jun 13 16:34:02 freenas kernel: re0: link state changed to DOWN
Jun 13 16:34:05 freenas kernel: re0: link state changed to UP
Jun 13 16:34:09 freenas 1 2022-06-13T16:34:09.202650-06:00 freenas.local dhclient 7740 - - New IP Address (re0): 192.168.0.178
Jun 13 16:34:09 freenas 1 2022-06-13T16:34:09.203861-06:00 freenas.local dhclient 7741 - - New Subnet Mask (re0): 255.255.255.0
Jun 13 16:34:09 freenas 1 2022-06-13T16:34:09.205025-06:00 freenas.local dhclient 7742 - - New Broadcast Address (re0): 192.168.0.255
Jun 13 16:34:09 freenas 1 2022-06-13T16:34:09.206171-06:00 freenas.local dhclient 7743 - - New Routers (re0): 192.168.0.1
Jun 13 16:43:05 freenas kernel: re0: link state changed to DOWN
Jun 13 16:43:09 freenas kernel: re0: link state changed to UP
Jun 13 16:43:10 freenas 1 2022-06-13T16:43:10.830901-06:00 freenas.local dhclient 7860 - - New IP Address (re0): 192.168.0.178
Jun 13 16:43:10 freenas 1 2022-06-13T16:43:10.832033-06:00 freenas.local dhclient 7861 - - New Subnet Mask (re0): 255.255.255.0
Jun 13 16:43:10 freenas 1 2022-06-13T16:43:10.833147-06:00 freenas.local dhclient 7862 - - New Broadcast Address (re0): 192.168.0.255
Jun 13 16:43:10 freenas 1 2022-06-13T16:43:10.834259-06:00 freenas.local dhclient 7863 - - New Routers (re0): 192.168.0.1
Jun 13 16:43:25 freenas kernel: re0: link state changed to DOWN
Jun 13 16:43:33 freenas 1 2022-06-13T16:43:33.881355-06:00 freenas.local dhclient 7884 - - New IP Address (re0): 192.168.0.178
Jun 13 16:43:33 freenas 1 2022-06-13T16:43:33.882472-06:00 freenas.local dhclient 7885 - - New Subnet Mask (re0): 255.255.255.0
Jun 13 16:43:33 freenas 1 2022-06-13T16:43:33.883569-06:00 freenas.local dhclient 7886 - - New Broadcast Address (re0): 192.168.0.255
Jun 13 16:43:33 freenas 1 2022-06-13T16:43:33.884709-06:00 freenas.local dhclient 7887 - - New Routers (re0): 192.168.0.1
Jun 13 16:43:34 freenas kernel: re0: link state changed to UP
I've turned off DHCP for this interface now. Do you think it's possible that turning on DHCP for this interface was possibly causing the network to stop responding at later times like this? If not, is there extra debugging I can turn on to try to troubleshoot this problem?