1333152322 Q * clopez Ping timeout: 480 seconds 1333155512 J * FireEgl FireEgl@2001:470:e056:1:25e9:bd96:95aa:f5a2 1333165807 J * clopez ~clopez@82.25.60.213.dynamic.mundo-r.com 1333171819 Q * clopez Ping timeout: 480 seconds 1333182164 J * ghislain ~AQUEOS@adsl2.aqueos.com 1333183033 N * Bertl_zZ Bertl 1333183037 M * Bertl morning folks! 1333183321 J * bonbons ~bonbons@2001:960:7ab:0:c558:2ea6:f6bd:87ed 1333184270 M * Bertl off for now ... bbl 1333184274 N * Bertl Bertl_oO 1333187333 J * ghislain1 ~AQUEOS@adsl2.aqueos.com 1333187718 Q * ghislain Ping timeout: 480 seconds 1333190587 Q * ensc|w Remote host closed the connection 1333190595 J * ensc|w ~ensc@www.sigma-chemnitz.de 1333195350 J * kir ~kir@swsoft-msk-nat.sw.ru 1333195440 P * kir 1333195870 Q * ghislain1 Quit: Leaving. 1333198719 Q * kcin Quit: ZNC - http://znc.in 1333198895 J * kcin ~kcin@91.118.96.132 1333200113 J * ghislain ~AQUEOS@adsl2.aqueos.com 1333205954 Q * ghislain Quit: Leaving. 1333206414 J * clopez ~clopez@82.25.60.213.dynamic.mundo-r.com 1333211743 Q * cuba33ci Read error: Connection reset by peer 1333211924 J * cuba33ci ~cuba33ci@114-36-228-201.dynamic.hinet.net 1333228444 M * Guy- hmmm... does vserver set some memory limits by default in 3.3.0-vs2.3.3.1 that it didn't set in 3.2.2-vs2.3.2.6? 1333228460 M * Guy- a guest is reporting "Could not reserve enough space for object heap" when starting java 1333228554 M * Guy- it appears to work if I strace it, though... :o 1333228604 M * Guy- yes, it works if I run it interactively via vserver enter, but not when run from the vserver's init 1333228716 M * Guy- ulimit -a says "max locked memory (kbytes, -l) 64" if run from init 1333228722 M * Guy- unlimited if run via vserver enter 1333228806 M * Guy- same for "stack size (kbytes, -s) 8192" 1333228893 M * Guy- but these are not what cause it 1333228928 M * Guy- mmap2(NULL, 3221225472, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = -1 ENOMEM (Cannot allocate memory) 1333228932 M * Guy- this is what fails 1333229180 M * Guy- looking in /dev/cgroup I see nothing suspicious 1333229937 M * Guy- starting Java with more conservative memory settings seems to work, but I fear the java app will run out of memory 1333229949 M * Guy- the exact same java command line worked with the previous kernel 1333230342 M * Guy- (the other difference between the two kernels, aside from the version, is that the new one uses SLAB instead of SLUB) 1333230993 M * Guy- memory.failcnt is still zero 1333232642 Q * bonbons Quit: Leaving