Here's what happened:
- freenas running on HP N54L with 5 x 1TB HDs encrypted and 8GB RAM (NON ECC) - ECC is ordered so this had to do for now
- system had been running for about 2 months, I did a reinstall in-between as I added an additional HD to the mix
- boots off 2 USB sticks that are mirrored
Yesterday, all working fine, I left for a barbeque, accessed the freenas remotely from my Android phone via a proxy and accessed a cifs share to check a picture.
Came home 4h later accessed the GUI which was open in my browser and clicked: check for update got a reply of cannot resolve host !? Tried changing DNS, etc, nothing helped. From my MacBook all good accessing the internet. I was still logged in via SSH and even from the cl I couldn't even ping anything outside my network.
I realized some cl commands showed this kind of error:
I checked memory and all was fine ,the freenas was basically idling...
I then decided to try a reboot. After the reboot the freenas wouldn't boot but show these errors when connecting a screen to it so I selected the second to last boot environment and it booted (while doing this I was connected via a network cable to my MacBook) - then moved the freenas to its proper place where I have no access to a screen and its booting but not getting an IP so I assume it's the same problem as above.
The only suspicion I have is the last change I did before leaving the house but I'm unsure how to reverse this from the command line:
- I had found errors in transmission's logs and after googling it I found a solution in these forums here: https://forums.freenas.org/index.ph...-receive-buffer-please-help.15203/#post-74611
The errors were something like this:
so accordingly to that thread I used the GUI to set these tunables:
both set to sysctl
Could this be the cause of my issues and how to revert this from the command line?
- freenas running on HP N54L with 5 x 1TB HDs encrypted and 8GB RAM (NON ECC) - ECC is ordered so this had to do for now
- system had been running for about 2 months, I did a reinstall in-between as I added an additional HD to the mix
- boots off 2 USB sticks that are mirrored
Yesterday, all working fine, I left for a barbeque, accessed the freenas remotely from my Android phone via a proxy and accessed a cifs share to check a picture.
Came home 4h later accessed the GUI which was open in my browser and clicked: check for update got a reply of cannot resolve host !? Tried changing DNS, etc, nothing helped. From my MacBook all good accessing the internet. I was still logged in via SSH and even from the cl I couldn't even ping anything outside my network.
I realized some cl commands showed this kind of error:
Code:
isc_socket_create: not enough free resources can't create socket - .... no buffer space available
I checked memory and all was fine ,the freenas was basically idling...
I then decided to try a reboot. After the reboot the freenas wouldn't boot but show these errors when connecting a screen to it so I selected the second to last boot environment and it booted (while doing this I was connected via a network cable to my MacBook) - then moved the freenas to its proper place where I have no access to a screen and its booting but not getting an IP so I assume it's the same problem as above.
The only suspicion I have is the last change I did before leaving the house but I'm unsure how to reverse this from the command line:
- I had found errors in transmission's logs and after googling it I found a solution in these forums here: https://forums.freenas.org/index.ph...-receive-buffer-please-help.15203/#post-74611
The errors were something like this:
Code:
UDP failed to set receive buffer: No buffer space available (tr-udp.c:58) UDP failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c77)
so accordingly to that thread I used the GUI to set these tunables:
Code:
kern.ipc.maxsockbuf=5242880 net.inet.udp.recvspace=5242880
both set to sysctl
Could this be the cause of my issues and how to revert this from the command line?