- November 26, 2019 at 10:37 am
I have recently installed VitalPBX on a Supermicro X7SPA-D525-HF. This is a passively cooled system. At the end of the install, which took a long tim, it started giving me temperature warnings. Luckily it finished before frying the CPU.
Then I did a yum update to bring the system to the latest version (2.3.8-3). This also installed a new kernel and during update-initramfs I was getting the same warnings again. It too took a while, so I am guessing during the install it may have been update-initramfs as well.
I am running Debian systems on other systems with the same hardware and never noticed anything like this. Yes, update-initramfs takes a while on them too, but not as long and it certainly does not heat the CPU as much.0
- November 26, 2019 at 4:00 pm
- November 26, 2019 at 5:03 pm
I am not sure I understand what you’re asking. This is a clean install from the ISO, followed by a yum update. Only installed what the ISO installer installed.
Not a multi-tennant system, if that’s what you’re asking.
There are 9 extensions and 2 trunks, but obviously those don’t affect the OS. I am not too familiar with CentOS. All the other systems I’ve built have been Debian pr Debian based.
I don’t recall if the same effect was present with Elastix.
Maybe it’s more of a CentOS question than a VitalPBX?0
- November 27, 2019 at 2:35 pm
- November 27, 2019 at 2:55 pm
- November 27, 2019 at 3:21 pm
- November 27, 2019 at 3:31 pm
Posted by: @erik
- December 1, 2019 at 10:53 am
That must be CentOS then. No virtualisation. It’s running on a Supermicro X7SPA-D525-HF, bare metal. This is a passively cooled system with an Atom processor.
There is clearly something wrong with your cooling!
Even the mainboard is passive cooled you need at least a good airflow with fans inside the enclosure.
See here and other google searches.
Sure the Installation and Update auf VitalPBX uses the CPU. This is normal. Even after hours of 100% CPU Load your system should not get too hot.0
- December 1, 2019 at 1:18 pm
The entire system is passively cooled and has been for 10+ years. There are no fans inside the enclosure. There is normal airflow.
Yes, it is to be expected that the installation and update of VitalPBX uses more CPU than normal operation, but that does not cause a noticeable rise in temperature. It is specifically during update-initramfs that the temperature went way up. Next time, I will be ready to collect more data.
Also, I never said it got too hot. It just got hot enough to raise temperature warnings on the BMC. Could it have sustained this level of operation for hours, maybe?
The point was that it got hot at all. I have been running Elastix on this system for many years and never noticed anything like this when installing or updating.
I don’t think Elastix ever got beyond Centos5, so maybe this is normal behaviour for Centos7. I have no data to compare and was wondering if anyone else has.0
- December 1, 2019 at 1:26 pm
Install a clean debian and install:
stress or stress-ng (CPU Stresstesting)
Then watch the Temps and try again with CentOS.
example for stresstesting:
stress -c 4
stress-ng -cpu 4
Share your temperature-results
Keep in mind that a Intel Atom D525 is not really a fast CPU (very slow). This is why the VitalPBX installation takes so long.0
- You must be logged in to reply to this topic.