ifup eth0 SIOCSIFFLAGS: Cannot allocate memory Failed to bring up eth0 Centos Network won't work after kernel update and reboot -

ifup eth0 SIOCSIFFLAGS: Cannot allocate memory Failed to bring up eth0 Centos Network won't work after kernel update and reboot

ifup eth0
SIOCSIFFLAGS: Cannot allocate memory
Failed to bring up eth0

This is on a Centos 5.5 machine with OpenVZ kernel 2.6.18-238.12.1.el5.028stab091.1PAE, I updated 3 systems with the same hardware to the same kernel and for some reason the network didn't come back.

This only happened once the first time I booted into the new kernel and hasn't happened again but this is a serious issue for those running systems from remote locations such as a datacenters.

I believe rebooting is what fixed everything or possibly removing and reloading the kernel module for the NIC.


This may be a sign of a bad motherboard or power supply, eventually the related system just wouldn't come back after a reboot and would not power up at all.  Further, before the system died weird and random things happened with grub needing to be reinstalled after being corrupted etc...


  • DRBD Slow Performance - 99.99 % [jbd2/drbd0-8] highiowait solution
  • Linux how to enable and disable NCQ
  • error code:0xc0000005 windows 2012 datacenter
  • cPanel how to change main IP to fix licensing issue
  • How to completely remove mdadm array
  • mdadm zero-superblock to solve md device created on root device
  • grubby fatal error: unable to find a suitable template solution Centos
  • Linux How To Recover Partition Table from Kernel and Restore Centos/Debian etc..
  • weird mv error mv: inter-device move failed:
  • Apache Log Error Message when starting
  • OpenVZ Migration Hostnode Containers from Centos 5 to Centos 6
  • Linux Mint 17 How to Enable File Sharing Option in File Manager
  • VBOX/Virtualbox how to resize the disk file image vdi
  • OpenVZ Error: Failed to load 2nd level quota solution
  • 99.99 % [jbd2/drbd0-8] highiowait
  • heartbeat cross talk
  • Openvz error solutions Container already locked (error) can't lock quota file, some quota operations are performing for id 1200
  • blocked for more than 120 seconds issues with iowait and timeout on Live Linux distribution while writing to physical disk
  • SELinux targeted policy relabel is required
  • possible SYN flooding on port 80. Sending cookies.