On Fri, 2011-02-25 at 16:47 +0100, Daniel Lezcano wrote: > Mmh, I don't remember exactly what I did (that was last year). But you > are right, the containers where spawned one after the other. I think I > was doing lxc-wait -n <name> -s RUNNING before running the next > container. As I have a 8 cores, that did not take so much time to boot > (2 minutes).
Interesting, I didn't know about lxc-wait. Thanks! > Google says you can setup these tables with the following values if you > encounter this problem. > > echo 256 > /proc/sys/net/ipv4/neigh/default/gc_thresh1 > echo 512 > /proc/sys/net/ipv4/neigh/default/gc_thresh2 > echo 1024 > /proc/sys/net/ipv4/neigh/default/gc_thresh3 > > Do they fix your problem ? I found that, but even with much larger values for the thresholds I'm still getting the error. Thanks Andre ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
