F5F Stay Refreshed Software Operating Systems Issues with Ubuntu 18.10 Home Server

Issues with Ubuntu 18.10 Home Server

Issues with Ubuntu 18.10 Home Server

K
KaisaSD2
Member
69
03-27-2021, 03:56 AM
#1
Every few days my Ubuntu server stops responding to the services I run (like PiHole, SMB, TimeMachine, SSH, Webmin, etc.), but the main Apache site still works. It seems to be a mix of hardware and software issues. Since I’m not using the LTS version, I need SMB_fruit in Samba. What should I try?
K
KaisaSD2
03-27-2021, 03:56 AM #1

Every few days my Ubuntu server stops responding to the services I run (like PiHole, SMB, TimeMachine, SSH, Webmin, etc.), but the main Apache site still works. It seems to be a mix of hardware and software issues. Since I’m not using the LTS version, I need SMB_fruit in Samba. What should I try?

J
JustRhune
Member
199
03-27-2021, 06:39 AM
#2
Review your logs carefully; the problem is likely there.
J
JustRhune
03-27-2021, 06:39 AM #2

Review your logs carefully; the problem is likely there.

F
FlowerAbby2
Junior Member
15
03-27-2021, 09:07 AM
#3
System started cleaning PHP session files on April 15 at 07:09. The process encountered issues loading php7.0. Several errors appeared, including missing dependencies and timeouts during device operations. The system attempted to restart services and handled cron jobs, but faced persistent failures with the swap partition.
F
FlowerAbby2
03-27-2021, 09:07 AM #3

System started cleaning PHP session files on April 15 at 07:09. The process encountered issues loading php7.0. Several errors appeared, including missing dependencies and timeouts during device operations. The system attempted to restart services and handled cron jobs, but faced persistent failures with the swap partition.

R
rebelka79
Member
185
04-03-2021, 05:09 PM
#4
Check the logs for issues when the system slows down. It seems Ubuntu 18 typically uses a swap file and is reporting it can't find sdb7. You might want to investigate that. Also, you can disable swap with "sudo swapoff -a" if you have sufficient RAM to run without it.
R
rebelka79
04-03-2021, 05:09 PM #4

Check the logs for issues when the system slows down. It seems Ubuntu 18 typically uses a swap file and is reporting it can't find sdb7. You might want to investigate that. Also, you can disable swap with "sudo swapoff -a" if you have sufficient RAM to run without it.

I
iTz_JustDizzy
Junior Member
46
04-04-2021, 01:53 PM
#5
Execute the commands to list disk blanks, show disk space, and display fstab details.
I
iTz_JustDizzy
04-04-2021, 01:53 PM #5

Execute the commands to list disk blanks, show disk space, and display fstab details.

N
Niclin13
Member
193
04-06-2021, 04:40 AM
#6
lsblk displays device information. Each entry shows the name, major/minor, usage, size, type, mount point, and mount status. Disks appear as md0, sdb, sdg, sdg1, and others. Mount points point to various partitions and temporary files. Usage percentages reflect space allocation. UUID values help identify specific devices reliably.
N
Niclin13
04-06-2021, 04:40 AM #6

lsblk displays device information. Each entry shows the name, major/minor, usage, size, type, mount point, and mount status. Disks appear as md0, sdb, sdg, sdg1, and others. Mount points point to various partitions and temporary files. Usage percentages reflect space allocation. UUID values help identify specific devices reliably.

A
AutumnTechMC
Member
64
04-06-2021, 11:09 AM
#7
A solid solution: 1. Remove Ubuntu Server 2. Switch to CentOS I faced this issue before, and in short I couldn’t locate a solution, encountered similar challenges on CentOS, though they don’t cause failures. Keep in mind this is my experience and results might differ.
A
AutumnTechMC
04-06-2021, 11:09 AM #7

A solid solution: 1. Remove Ubuntu Server 2. Switch to CentOS I faced this issue before, and in short I couldn’t locate a solution, encountered similar challenges on CentOS, though they don’t cause failures. Keep in mind this is my experience and results might differ.

L
LimoLama
Member
89
04-06-2021, 07:46 PM
#8
Importing the raid array can be challenging. The main problem is using Debian/Ubuntu due to limited support for the Unifi controller. Running freeNAS with Jails or VMs is appealing, but your current server lacks the necessary power.
L
LimoLama
04-06-2021, 07:46 PM #8

Importing the raid array can be challenging. The main problem is using Debian/Ubuntu due to limited support for the Unifi controller. Running freeNAS with Jails or VMs is appealing, but your current server lacks the necessary power.