ifconfig: socket(AF_INET6), SOCK_DGRAM): No buffer space available

[MtK]

Hey,
I just updated my 9.10 to the latest release (from today?) and after reboot my server is inaccessible.

Looking through IPMI I see a lot of IFCONFIG errors, preventing everything from starting (NGINX, Jails, etc).

Is this a known bug?

M.

 

[dlavigne]

Depends upon what the errors are. Use Insert -> Code when you paste them.

 

[MtK]

Depends upon what the errors are. Use Insert -> Code when you paste them.

I can't really copy anything because the console is also inaccessible. I can see but not mark/select/type anything.

and I do see:

Code:

Init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs

after 30 seconds the screen scrolls several times as if a key is (stuck) pressed.
(no I don't have any keyboard connected)

 

[dlavigne]

That could be caused by a failed boot device. It is worth installing the latest 9.10 STABLE to another stick, booting from that, and seeing if the issue is resolved.

 

[MtK]

That could be caused by a failed boot device. It is worth installing the latest 9.10 STABLE to another stick, booting from that, and seeing if the issue is resolved.

I was just able to revert to the previous version and the server booted :/

 

[MtK]

updated again to version 20160627 and the same issue returned!

 

[dlavigne]

Interesting. Is it anything like https://bugs.freenas.org/issues/16141?

 

[MtK]

Interesting. Is it anything like https://bugs.freenas.org/issues/16141?

Nope

 

[dlavigne]

Someone else just created this one which has your error: https://bugs.freenas.org/issues/16150

 

[MtK]

Someone else just created this one which has your error: https://bugs.freenas.org/issues/16150

Thanks!
though not sure it's the same underlying issue.

 

[avalon60]

My problem is that FreeNAS goes into a loop with this line coming up over and over again:

Init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs

I created the bug report

 

[MtK]

My problem is that FreeNAS goes into a loop with this line coming up over and over again:

Init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs

I created the bug report

yes, in my case I had the same *final* message with the same *final* result of looping every 30 seconds.
I added some more detailed to the bug report.

 

[MtK]

Issue still exists after updating to 9.10.1!

 

[jah_liar]

I have the same problem after upgrading my 9.10 some days ago.

I first tried to upgrade from 9.3 to 9.10 (which worked well until some update broke it). Then I did a fresh install with 9.10.1 which worked until I restored my settings and did a reboot. Same behavior now.

It seems the system is not able to get networking up on boot - it does not find the route to the default gateway and therefore doesn't configure the interface (which is set to DHCP).

The only configuration I can get to run is the 9.10.1 initial install. I do have two jails (standard, one of them running nginx) on autostart so maybe they play some role here.

My box is the HP ProLiant N54L (Celeron) with 10 GB ECC RAM.

Any hints are appreciated. I am happy to supply logs/more information if you let me know what you need...

 

[MtK]

I made a backup of the config, installed a fresh 9.10.1 on one of the mirrored USBs and restored the config - all works fine, even reboot.
I mirrored the Boot with the other USB and system fails to boot!

 

[jah_liar]

I have the same problem after upgrading my 9.10 some days ago [...]

It seems that the problem was caused by sysctl values created by autotune and carried over from some old version. After restoring my settings manually everything works as expected.

It would be nice to have an option to ignore sysctl values when restoring a config file, or at least to have the chance to make modifications before the mandatory reboot. Right now, broken sysctls make the saved config file useless.

 

[MtK]

It seems that the problem was caused by sysctl values created by autotune and carried over from some old version. After restoring my settings manually everything works as expected.

It would be nice to have an option to ignore sysctl values when restoring a config file, or at least to have the chance to make modifications before the mandatory reboot. Right now, broken sysctls make the saved config file useless.

Well, it'd be better for FreeNAS to detect those and convert them into the correct form (mine were all autotune generated) or just disabled with a relevant popup/log message.