new_server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| new_server [2017/07/23 18:31] – josh | new_server [2018/01/16 10:35] (current) – josh | ||
|---|---|---|---|
| Line 89: | Line 89: | ||
| Latency | Latency | ||
| 1.97, | 1.97, | ||
| - | |||
| - | |||
| - | ====== Issues ====== | ||
| - | |||
| - | ===== APC UPS not killing power ===== | ||
| - | |||
| - | I think this is a Fedora / systemd problem. apcupsd will detect the AC power failure and initiate a shutdown (shutdown -h -H now via apccontrol). But apccontrol killpower does not seem to be called. Also, during shutdown, systemd reports "A stop job is running for APC UPS Power Control Daemon for Linux" | ||
| ====== Installation ====== | ====== Installation ====== | ||
| Line 140: | Line 133: | ||
| ====== Services ====== | ====== Services ====== | ||
| + | ^ Server ^ Services ^ OS ^ Hardware ^ | ||
| + | | anubis (host) | < | ||
| + | * apcupsd | ||
| + | * NFS | ||
| + | * KVM (libvirt-guests) | ||
| + | * gmail backups | ||
| + | * NFS backups | ||
| + | </ | ||
| + | | oneill (VM) | < | ||
| + | * HTTP | ||
| + | * wiki | ||
| + | * tt-rss | ||
| + | * mythweb (proxy) | ||
| + | * cameras (proxy) | ||
| + | * cgit (proxy) | ||
| + | </ | ||
| + | | carter (VM) | < | ||
| + | * git-daemon | ||
| + | * gitolite git hosting over ssh | ||
| + | * cgit | ||
| + | </ | ||
| + | | baal (VM) | < | ||
| + | * openvpn | ||
| + | * squid proxy | ||
| + | </ | ||
| + | | hathor (VM) | < | ||
| + | * minetest | ||
| + | </ | ||
| + | | ra (VM) | < | ||
| + | * mythtv backend | ||
| + | * mythweb | ||
| + | </ | ||
| + | |||
| + | ====== Issues ====== | ||
| + | |||
| + | ===== APC UPS not killing power ===== | ||
| + | |||
| + | I think this is a Fedora / systemd problem. apcupsd will detect the AC power failure and initiate a shutdown (shutdown -h -H now via apccontrol). But apccontrol killpower does not seem to be called. Also, during shutdown, systemd reports "A stop job is running for APC UPS Power Control Daemon for Linux" | ||
| + | |||
| + | Bug report filed: [[https:// | ||
| + | |||
| + | ===== M.2 PCIe NVMe drive disappearing ===== | ||
| + | |||
| + | Three times now my server has stopped responding and shows a blank console. After resetting and going into the UEFI setup the Western Digital M.2 drive no longer shows up. After a poweroff and cold boot, the drive reappears in UEFI setup and I have to reset my boot settings to select it as the default boot entry. The system appears to run properly after this until the next time. | ||
| + | |||
| + | The problem I'm observing seems very similar to this: [[https:// | ||
| + | |||
| + | After the third time this happened, on 2017-12-13, I updated the UEFI firmware on the ASRock motherboard to version 3.30. The upgrade was successful, and after resetting my options (particularly re-enabling SVM and power on after AC loss), the system appears to be running properly again now. | ||
| + | |||
| + | On 2017-12-15 the system froze again. I disabled "C6 Mode" in the UEFI setup and started up again. | ||
| + | |||
| + | 2017-12-17: I have not observed the problem since disabling "C6 Mode", but I have a feeling it will still come back and could be related to NVMe APST modes. Similar problem here: [[https:// | ||
| + | |||
| + | < | ||
| + | nvme_core.default_ps_max_latency_us=0 | ||
| + | </ | ||
| + | |||
| + | Now '' | ||
| + | |||
| + | Turned "C6 Mode" back on but have not observed the M.2 drive disappearing problem again with APST disabled. | ||
| + | |||
| + | ===== BUG: soft lockup ===== | ||
| + | |||
| + | A few times after fixing the M.2 drive disappearing issue, my server has frozen. One of the times I caught the console output which listed several messages like " | ||
| + | |||
| + | On 2018-01-08, I upgraded from kernel 4.14.4 to 4.14.11 and added " | ||
| + | |||
| + | 2018-01-09: Igor seems to be experiencing the same bug and pointed me to https:// | ||
| + | |||
| + | 2018-01-15: Got the freeze again after disabling C6 mode in setup. I looked deeper in setup options and found the buried " | ||
new_server.1500849078.txt.gz · Last modified: by josh
