I manages many server using Ubuntu Server for hosting dotnet apps as service. Recently, they failed one by one. The dotnet services on them cannot start. When typing dotnet –version, it reports
A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist.
The whole problem is we installed the dotnet very early. In that time, we need to install the packages-microsoft-prod due to lack of official support of dotnet from ubuntu. But now it’s changed. Recently, dotnet is listed in the Ubuntu package manager feeds. That leads into the conflict which cause the services cannot start.
The way to fix is easy:
First, lists all installed packages using
sudo apt list --installed | grep dotnet
You may see some like dotnet-host dotnet-hostfxr-6.0 dotnet-runtime-6.0.
Now, removes those package listed using
sudo apt purge dotnet-host dotnet-hostfxr-6.0 dotnet-runtime-6.0
Also, packages-microsoft-prod is need to be purged also. To be mentioned, it must be purged instead of removed, which will remove the config file which is very the reason cause the conflicts.
sudo dpkg -P packages-microsoft-prod
Now, we can install the dotnet runtime from ubuntu official feeds using some like
sudo apt update && \
sudo apt install -y aspnetcore-runtime-6.0
Hope this can save your day.
I have a server using Ubuntu Server 22.04 LTS with nginx and php supported for a long time. Today, after I fire a regular update by using apt update, apt upgrade and a reboot, my web server is down.
When checking the status of nginx, it reports that port 80 is taken:
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Unknown error)
And the lsof command
lsof -i -P -n | grep LISTEN
reports that port 80 is used by apache2. That’s really weird. This server never has apache configured or started. Who wanna run apache aside nginx in a production environment, uhh?
By checking the log of apt, I found that php8.1 is upgraded with a library named libapache2-mod-php8.1 installed automatically. I don’t find any log related to apache installation. Maybe the apache2 is preinstalled for a very long time but never initiated but the libapache2-mod-php8.1 upgrading process triggered it on.
After I purge apache2* and libapache2-mod-php8.1, the nginx can be restarted without any problem.
Ubuntu, including server, 20.04 is launched several days ago. Many servers with 19.10 or earlier system are planed to upgrade soon. There are some issues should be noticed before you process.
1. If do-release-upgrade returns nothing found, you may want to use
2. Some servers will be stuck with “Updating database of manual pages” process. In my tests on about 20 servers, about 20% servers will pass it with no more than 2 minutes delay. More than half servers, mainly on Azure, stuck there for 20-40 minutes. During this time, around 100 GB data are read from disk with 100% CPU using, reported by Azure portal. I don’t know what it read. All my files on the server cost no more than 20GB disk space. One of my server, hosted on Azure, costs more than half day so far (and not finished yet), more than 200GB data read. One server failed in that step, SSH drop and cannot reconnect at all. Before this problem solved, I strongly NOT recommend to upgrade your product server.
Update: The one stuck on Azure resume to idle after 14 hrs, 626.14GB reading and 27GB writing. Due to dead SSH process, I have to try to reboot the server. But the server never come back online. A kernel panic captured by Azure console while booting:
Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1010-azure #10-Ubuntu
Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017
Kernel Offset: 0x30000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
3. Upgrading will replace php 7.3 with 7.4. If some site is powered by php-fpm with Nginx, you may need to change your web site configuration file in Nginx available sites folder. All packages installed by pip3 will be dropped, not uninstalled properly. You may want to uninstall them if you don’t want to use it any more before upgrading system. Or, you can reinstall them after upgrading.
Every time when I log on my ubuntu server, there always be a System Information displayed. How can we tell to the bash to re-display this screen again?
The command is: landscape-sysinfo
Simply, you just need to type land and press tab key to let the auto complete do the job.
This command can be used to lock a file.
usage: chattr +i filename
The files locked by chattr cannot be modified or deleted, even with root permission.
For unlocking, use chattr -i filename.