ISPconfig on kvm
Sorry for bothering you - but about one year of googling along with trial-and-error did not solve the topic.
I am running ISPconfig3, based on Debian lenny, as a kvm-guest on a proxmox-server. The setup caused no problems whatsoever, but from 4 GB of memory assigend to the guest, only 885 MB are recognized and used.
And this causes mysql to produce a repeating failure:
ERROR 1135 (00000): Can't create a new thread (errno 12); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug.
Anyone has an idea about this strange behaviour ?
What are the outputs of
Do you use a 32- or 64-bit OS?
Free tells me:
total used free shared buffers cached
Mem: 906284 890700 15584 0 4360 293740
-/+ buffers/cache: 592600 313684
Swap: 2896032 924356 1971676
ispconfig:~# cat /proc/meminfo
MemTotal: 906284 kB
MemFree: 18628 kB
Buffers: 5320 kB
Cached: 291548 kB
SwapCached: 269192 kB
Active: 612400 kB
Inactive: 252104 kB
SwapTotal: 2896032 kB
SwapFree: 1971676 kB
Dirty: 220 kB
Writeback: 0 kB
AnonPages: 561436 kB
Mapped: 31028 kB
Slab: 12748 kB
SReclaimable: 7516 kB
SUnreclaim: 5232 kB
PageTables: 3368 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 3349172 kB
Committed_AS: 3737948 kB
VmallocTotal: 122564 kB
VmallocUsed: 3572 kB
VmallocChunk: 118732 kB
Hugepagesize: 4096 kB
the ispconfig is running a 2.6.26-2-486 #1 Sat Jun 11 14:47:34 UTC 2011 i686 GNU/Linux; the kvm-host is running 2.6.32-4-pve #1 SMP Mon May 9 12:59:57 CEST 2011 x86_64 GNU/Linux.
Can you post the output of
2.6.26-2-486 #1 Sat Jun 11 14:47:34 UTC 2011 i686 GNU/Linux
And what you mean with correct results ?
Do the commands show the correct amount of RAM on the host?
No - we assigned 4 GB on the kvm-host. The ispconfig-guest only knows about 900 MB. This looks like the basic problem - why mysql can`t fork any further threads.
I understand, but do the commands show the correct amount of RAM (4GB) on the host?
The host got 8 GB of Ram, 2 other guests are running on this host, too.
And the 8 gb are fully recognized. Installing a new kernel (2.6.26-2-amd64) at least solved it - but I would still like to know why this could happen.
This is what I've found:
|All times are GMT +2. The time now is 09:56.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.