On Fri, 20 Jan 2017 14:44:57 +0000 Mike Blumenkrantz <michael.blumenkra...@gmail.com> said:
> seems fixed now it is indeed back down. this started yesterday... mysqld is actually up and running... i don't know what's up. i tried to just shut6 down mysql, phd, apache and restart. dmesg had a bunch of out of memory errors in them. i see it again: [48726.582216] Out of memory: Kill process 1394 (mysqld) score 278 or sacrifice child [48726.582222] Killed process 1394 (mysqld) total-vm:1976348kB, anon-rss:1124260kB, file-rss:0kB i restarted mysql now and it's running... but something does seem to have gone very wrong. :( i have tried the following: reduce max # of apache servers from 300 to 30 (max clients 30, max spare servers 3, min spare 1). reduced mysql innodb buffer pool from 800 to 600m i don't know but the oom message in the kernel shows 111 apache processes (it looks like) running at the time the oom happened and killed mysql... let's see what gives now. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
