OMV Server running hot after upgrade to 4.x

    • OMV 4.x
    • Upgrade 3.x -> 4.x
    • OMV Server running hot after upgrade to 4.x

      I upgraded my server from 3.x to 4.x and since the upgrade it has been running hot. I haven't added any new service after the upgrade that wasn't running on 3.x. The only other change I see is the 3x increase in the number of processes running.

      Attached are the graphs.

      Processes:
      Memory:
      Processor:
      Temperature:
    • peekaa wrote:

      look at commands top and journalctl, what is wrong. I did today upgrade too, and this helped me. FE. i had to start and then stop monitoring, to stop some error "rrdcached plugin failed to connect to rrdcached", than I had to add to samba ntlm auth = yes to be able to connect with my media player and xp.
      Any tips on what I should be looking at? I don't have outputs from before the upgrade so I won't know what it causing it. So far I can see ~3% CPU usage by the VBox plugin, but I've always used it.

      The only errors I see in the syslogs are:

      Source Code

      1. Jul 1 02:24:04 Vault PlexMediaServer: Error parsing XML.
      2. Jul 1 02:24:04 Vault PlexMediaServer: Error parsing XML.
      3. Jul 1 04:12:54 Vault cron-apt: TypeError: 'NoneType' object is not callable
      4. Jul 1 04:12:54 Vault cron-apt: TypeError: 'NoneType' object is not callable

      David B wrote:

      Off-topic question: How are you tracking system temperature?
      I use SNMP plugin and send my info to LibreNMS running in a Virtual Machine.
    • utamav wrote:

      I upgraded my server from 3.x to 4.x and since the upgrade it has been running hot. I haven't added any new service after the upgrade that wasn't running on 3.x. The only other change I see is the 3x increase in the number of processes running.
      While the increased number of processes is interesting:
      With all other factors being equal (cpu fan speed, ambient room temperature), it's CPU load that would have the greatest bearing on the CPU's temp. In your case, your CPU is not being stressed at all with either OMV3 or OMV4. There's no reason why your CPU temperature should have jumped like that, with roughly the same load.

      Since actual CPU load hasn't changed, from OMV3 to 4, and the jump in CPU temp is massive; I'd be suspicious of the temperature data in the chart or (it would have to be a wild coincidence) something has happened to the CPU fan.

      Another possibility to look at is fan speed in BIOS, if your BIOS supports it. You might be able to pin the fan to full speed, in BIOS, and see what the results are. Pinning your CPU fan to a higher speed in BIOS might fix the issue. (On the other hand, even a slow fan speed should work in your case - your CPU is not working hard.)

      On the command line, see if the output of the following agrees with the charts.
      sensors
      ____________________________________________________

      As an example, with a load bouncing between 0 to 3%, the output of sensors on my i3 box is as follows:

      acpitz-virtual-0
      Adapter: Virtual device
      temp1: +27.8°C (crit = +105.0°C)
      temp2: +29.8°C (crit = +105.0°C)

      coretemp-isa-0000
      Adapter: ISA adapter
      Physical id 0: +34.0°C (high = +80.0°C, crit = +100.0°C)
      Core 0: +31.0°C (high = +80.0°C, crit = +100.0°C)
      Core 1: +33.0°C (high = +80.0°C, crit = +100.0°C)

      ____________________________________________________

      Depending on the generation of CPU you have, Intel processors self regulate for temperature meaning they slow down if they get excessively hot. On the other hand, anything north of 80C is not good for long life.

      (BTW - for followup - I'm out of town until next weekend, starting tomorrow.)

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.13, Intel Server SC5650HCBRP, 6GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      2nd Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • Source Code

      1. acpitz-virtual-0
      2. Adapter: Virtual device
      3. temp1: +70.0°C (crit = +104.0°C)
      4. coretemp-isa-0000
      5. Adapter: ISA adapter
      6. Physical id 0: +71.0°C (high = +87.0°C, crit = +105.0°C)
      7. Core 0: +67.0°C (high = +87.0°C, crit = +105.0°C)
      8. Core 1: +72.0°C (high = +87.0°C, crit = +105.0°C)
      Display All

      Source Code

      1. top - 16:29:14 up 1 day, 5:50, 1 user, load average: 0.04, 0.06, 0.08
      2. Tasks: 213 total, 1 running, 209 sleeping, 0 stopped, 3 zombie
      3. %Cpu(s): 0.9 us, 0.6 sy, 0.0 ni, 98.4 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st
      4. KiB Mem : 8034376 total, 496160 free, 1948840 used, 5589376 buff/cache
      5. KiB Swap: 4789244 total, 4722708 free, 66536 used. 5680384 avail Mem
      6. Unknown command - try 'h' for help
      7. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
      8. 3380 vbox 20 0 2487964 67944 39196 S 2.6 0.8 69:19.68 VBoxHeadless
      9. 2821 unms 20 0 901272 223224 9936 S 1.7 2.8 30:07.25 node
      10. 12328 userm 20 0 42952 3736 2976 R 1.0 0.0 0:01.28 top
      11. 902 root 20 0 1182680 29012 3932 S 0.7 0.4 9:40.43 dockerd
      12. 706 vbox 20 0 667416 14948 10776 S 0.3 0.2 1:44.87 VBoxSVC
      13. 1387 root 20 0 646608 11476 2252 S 0.3 0.1 8:36.61 docker-containe
      14. 1797 unms 20 0 18536 3628 1556 S 0.3 0.0 4:22.54 redis-server
      15. 1811 root 20 0 7648 4136 3316 S 0.3 0.1 0:55.79 docker-containe
      16. 1911 plex 35 15 1857968 49228 7768 S 0.3 0.6 4:57.35 Plex Script Hos
      17. 2424 unms 20 0 158888 41460 2800 S 0.3 0.5 5:24.45 ruby
      18. 8959 root 20 0 0 0 0 S 0.3 0.0 0:01.15 kworker/0:2
      19. 1 root 20 0 205252 6360 4084 S 0.0 0.1 0:09.85 systemd
      20. 2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
      Display All



      Source Code

      1. -- Logs begin at Sat 2018-06-30 14:24:18 CDT. --
      2. Jul 01 16:15:04 vault snmpd[907]: Connection from UDP: [10.0.x.8]:40548->[10.0.x.10]:161
      3. Jul 01 16:15:04 vault snmpd[907]: Connection from UDP: [10.0.x.8]:40548->[10.0.x.10]:161
      4. Jul 01 16:15:04 vault snmpd[907]: Connection from UDP: [10.0.x.8]:40548->[10.0.x.10]:161
      5. Jul 01 16:15:04 vault snmpd[907]: Connection from UDP: [10.0.x.8]:40548->[10.0.x.10]:161
      6. Jul 01 16:15:04 vault snmpd[907]: Connection from UDP: [10.0.x.8]:40548->[10.0.x.10]:161
      7. Jul 01 16:15:04 vault snmpd[907]: Connection from UDP: [10.0.x.8]:40548->[10.0.x.10]:161
      8. Jul 01 16:15:04 vault snmpd[907]: Connection from UDP: [10.0.x.8]:40548->[10.0.x.10]:161
      9. Jul 01 16:15:17 vault sudo[11701]: pam_unix(sudo:session): session closed for user root
      10. Jul 01 16:15:27 vault sudo[11907]: userm : TTY=pts/0 ; PWD=/home/userm ; USER=root ; COMMAND=/bin/journalctl -f
      11. Jul 01 16:15:27 vault sudo[11907]: pam_unix(sudo:session): session opened for user root by userm(uid=0)
      12. Jul 01 16:16:01 vault CRON[11929]: pam_unix(cron:session): session opened for user unms by (uid=0)
      13. Jul 01 16:16:01 vault CRON[11930]: (unms) CMD (/home/unms/app/update.sh --cron > /dev/null 2>&1 || true)
      14. Jul 01 16:16:01 vault CRON[11929]: pam_unix(cron:session): session closed for user unms
      15. Jul 01 16:17:01 vault CRON[11968]: pam_unix(cron:session): session opened for user unms by (uid=0)
      16. Jul 01 16:17:01 vault CRON[11967]: pam_unix(cron:session): session opened for user root by (uid=0)
      17. Jul 01 16:17:01 vault CRON[11969]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
      18. Jul 01 16:17:01 vault CRON[11970]: (unms) CMD (/home/unms/app/update.sh --cron > /dev/null 2>&1 || true)
      19. Jul 01 16:17:01 vault CRON[11968]: pam_unix(cron:session): session closed for user unms
      20. Jul 01 16:17:01 vault CRON[11967]: pam_unix(cron:session): session closed for user root
      21. Jul 01 16:18:01 vault CRON[12010]: pam_unix(cron:session): session opened for user unms by (uid=0)
      22. Jul 01 16:18:01 vault CRON[12011]: (unms) CMD (/home/unms/app/update.sh --cron > /dev/null 2>&1 || true)
      23. Jul 01 16:18:01 vault CRON[12010]: pam_unix(cron:session): session closed for user unms
      Display All

      The post was edited 3 times, last by utamav ().

    • While you may have more tasks running, it appears that nearly all are sleeping which would have little effect on CPU load.
      _________________________________________________________________________

      It seems that you have a hot box, literally. I think your "temp1:" is you mobo temperture sensor, running at 158F. The inside of your server is, decidedly, "warm".

      Also, while warm, 67c and 72C CPU (152 to 161F) core temps are way under the 76 to 82C (169 to 179F) span shown in the chart. Did you look at the chart at the same time you pulled the sensors output? Did they match?

      Lastly, as it seems, your i7 CPU can endure higher temps than my i3 can.
      ___________________________________________________

      Still, I'd look at BIOS to see if the CPU fan speed can be increased. I'd also look at ways to vent the box, with an additional case fan if necessary, to get your server's overall temp's down. (Check to make sure that your case's vented surfaces are not blocked - this would include cases with vented bottoms that are sitting on carpet. Put a piece of plywood under it, or something else that's hard so the case sits on it's legs AND has a gap for air flow.) Getting a better CPU fan is not a bad idea either.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.13, Intel Server SC5650HCBRP, 6GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      2nd Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • I still can't get on board with the idea that the motherboard temp and CPU (all of them), jumped roughly 20 degrees C, after an upgrade. (Unless, of course, something is restricting air flow to the case.)

      Just for testing purposes, if it was me, I'd rebuild OMV3 on a usb thumbdrive for side-by-side comparison. (But that's the OCD in me.)

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.13, Intel Server SC5650HCBRP, 6GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      2nd Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • flmaxey wrote:

      While you may have more tasks running, it appears that nearly all are sleeping which would have little effect on CPU load.
      _________________________________________________________________________

      It seems that you have a hot box, literally. I think your "temp1:" is you mobo temperture sensor, running at 158F. The inside of your server is, decidedly, "warm".

      Also, while warm, 67c and 72C CPU (152 to 161F) core temps are way under the 76 to 82C (169 to 179F) span shown in the chart. Did you look at the chart at the same time you pulled the sensors output? Did they match?

      Lastly, as it seems, your i7 CPU can endure higher temps than my i3 can.
      ___________________________________________________

      Still, I'd look at BIOS to see if the CPU fan speed can be increased. I'd also look at ways to vent the box, with an additional case fan if necessary, to get your server's overall temp's down. (Check to make sure that your case's vented surfaces are not blocked - this would include cases with vented bottoms that are sitting on carpet. Put a piece of plywood under it, or something else that's hard so the case sits on it's legs AND has a gap for air flow.) Getting a better CPU fan is not a bad idea either.
      The temp1 temperature is off between the graph and the sensor output by almost 20c but other temperature readings are close.

      If I am going to create a fresh copy of OMV, I'll probably start with OMV 4.x to see how that compares. Thanks for the tips and help.
    • utamav wrote:

      The temp1 temperature is off between the graph and the sensor output by almost 20c but other temperature readings are close.
      If I am going to create a fresh copy of OMV, I'll probably start with OMV 4.x to see how that compares. Thanks for the tips and help.
      As I understand the start of this thread, the problem developed after an upgrade from OMV3 to OMV4 (Was it a command line upgrade?)

      Just remember that you could do a clean OMV install using a CD as the source, and put the installation on a USB drive, leaving your current OMV4 installation alone and intact. (You might need to change the boot order in BIOS to boot from USB.)

      Depending on what you boot - you could do a side by side comparison.

      Another factor to consider, if you did a command line upgrade:
      Something could have gone wrong with the upgrade. It might be worth the time to build a USB thumbdrive (with OMV4) just to check out this possibility.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.13, Intel Server SC5650HCBRP, 6GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      2nd Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk