So I've never had this happen before. A DC tech opened a ticket with me and told me that 'Your machine 1638CC-XEON is beeping due to it being out of memory. Please check into this issue and advise.'
So I checked logs and all I could see is where some containers are running out of memory and openvz is killing some processes in their container like it should. I checked the disks and temp sensors in the server to make sure it wasn't 'beeping' for some other reason. Check out the ticket correspondence.
Them: Sierra, Your machine 1638CC-XEON is beeping due to it being out of memory. Please check into this issue and advise. Thanks,
Me: I've never heard of an out of memory beep. Naturally linux uses a lot of the RAM for disk cache but will free that up at anytime. (about 12GB used for cache). free -m total used free shared buffers cached Mem: 32014 31718 295 0 920 11857 -/+ buffers/cache: 18940 13073 Swap: 34815 3701 31114 So then I checked the disks with smartctl and they all appear to be good. Then I checked the temp sensors and they all seem good. (all under 31C) Can you confirm the 'out of memory beep' with a manual link or something?
Them: Sierra, Log into IPMI and you will see the Out of memory messages posted. Thanks,
Me: I am currently unable to login to IPMI on this machine but I did check dmesg and it looks like the last time there was an OOM from openvz was about 12 days ago. Is the machine beeping when there is DMESG errors being printed to console?
Them: Sierra, I have attached an image of the error message the device is throwing. Also are you using the public IPMI address as we are able to log into IPMI.
Me: Yes, it's just that I'm on linux right now. I'm also not seeing any 'attachments'.
Them: Sierra, Attachment are at the top of the ticket.
Me: Ok I read that, and it appears some containers on the node are running out of memory.... and OpenVZ is doing its job and killing processes in that container. Nothing to worry about. Can you please confirm that my server is beeping due to these dmesg logs being printed to the console?
Them: Sierra, Our on-site tech confirmed the beeping is due to the device running out of memory, how would you like us to proceed?
Me: I don't understand. The server is not out of memory.
So I checked logs and all I could see is where some containers are running out of memory and openvz is killing some processes in their container like it should. I checked the disks and temp sensors in the server to make sure it wasn't 'beeping' for some other reason. Check out the ticket correspondence.
Them: Sierra, Your machine 1638CC-XEON is beeping due to it being out of memory. Please check into this issue and advise. Thanks,
Me: I've never heard of an out of memory beep. Naturally linux uses a lot of the RAM for disk cache but will free that up at anytime. (about 12GB used for cache). free -m total used free shared buffers cached Mem: 32014 31718 295 0 920 11857 -/+ buffers/cache: 18940 13073 Swap: 34815 3701 31114 So then I checked the disks with smartctl and they all appear to be good. Then I checked the temp sensors and they all seem good. (all under 31C) Can you confirm the 'out of memory beep' with a manual link or something?
Them: Sierra, Log into IPMI and you will see the Out of memory messages posted. Thanks,
Me: I am currently unable to login to IPMI on this machine but I did check dmesg and it looks like the last time there was an OOM from openvz was about 12 days ago. Is the machine beeping when there is DMESG errors being printed to console?
Them: Sierra, I have attached an image of the error message the device is throwing. Also are you using the public IPMI address as we are able to log into IPMI.
Me: Yes, it's just that I'm on linux right now. I'm also not seeing any 'attachments'.
Them: Sierra, Attachment are at the top of the ticket.
Me: Ok I read that, and it appears some containers on the node are running out of memory.... and OpenVZ is doing its job and killing processes in that container. Nothing to worry about. Can you please confirm that my server is beeping due to these dmesg logs being printed to the console?
Them: Sierra, Our on-site tech confirmed the beeping is due to the device running out of memory, how would you like us to proceed?
Me: I don't understand. The server is not out of memory.
Last edited by a moderator: