1/7/2024 0 Comments Apache async http clientWhen OverlayFS is disabled but the boot partition is left as read only, it will set the boot to writable and reboot. Every time the PiOS booting, this script will be run. ĭescription=Disable Boot RO when Overlay DisabledĬonditionPathExists=/usr/local/sbin/disablebootro.shĮxecStart=/usr/local/sbin/disablebootro.shĪnd set the service start with system by this command: systemctl enable rvice Now, let’s create a systemd service to run this script when booting by create a file /etc/systemd/system/rvice with the content below. chmod +x /usr/local/sbin/disablebootro.sh Then, assign permission to this script for running by this command below. OverlayFS=$(/usr/bin/raspi-config nonint get_overlay_now)īootRO=$(/usr/bin/raspi-config nonint get_bootro_conf) usr/bin/raspi-config nonint disable_bootroĪnd this is for the new releases: #!/bin/sh usr/bin/raspi-config nonint get_bootro_conf usr/bin/raspi-config nonint get_overlay_now Here is the version for the old silenced raspi-config: #!/bin/sh Of cause, don’t do that with OverlayFS enabled. Now, let’s create the script named /usr/local/sbin/disablebootro.sh on your disk. The lucky thing is the raspi-config seems not be upgraded by apt command. For new ones, you will get a 1 printed directly after the command /usr/bin/raspi-config nonint get_overlay_now processed and the exit code will always set to 0. For the old releases, nothing will be printed but a 1 is printed when you run echo $? after that. You can check your version by running such a command /usr/bin/raspi-config nonint get_overlay_now when OverlayFS is not enabled. But it changed recently to print the result directly without setting the exit code. Sadly, there are two version of the script, based on the version of raspi-config.įor early releases of PiOS, raspi-config command line returns nothing but set the exit code. In another word, when disabling both OverlayFS and Boot partition ReadOnly, the PiOS need to be reboot twice.įor easing the process for disabling both OverlayFS and change the boot partition back to writable, I write a script to set the boot partition writable when OverlayFS is not enabled currently. But when enabling OverlayFS, raspi-config has an option to set the boot partition to read-only at the same time before rebooting. While disabling OverlayFS through raspi-config, there is no way to set the boot partition back to read-write before OverlayFS disabled, which requires a reboot. The problem is due to the read-only of the main partition, the mounting mode (readonly or read-write) cannot be changed when OverlayFS enabled. Boot partition can be set to read-only by raspi-config or editing fstab config file. The protection of OverlayFS doesn’t cover the boot partition (the first one). When enabled, the main partition (the second one) will be locked. PiOS shipped with Overlay FileSystem support. QNAP removed sleep function on new NAS products Maybe the apache2 is preinstalled for a very long time but never initiated but the libapache2-mod-php8.1 upgrading process triggered it on.Īfter I purge apache2* and libapache2-mod-php8.1, the nginx can be restarted without any problem. I don’t find any log related to apache installation. Who wanna run apache aside nginx in a production environment, uhh?īy checking the log of apt, I found that php8.1 is upgraded with a library named libapache2-mod-php8.1 installed automatically. This server never has apache configured or started. When checking the status of nginx, it reports that port 80 is taken: nginx: bind() to 0.0.0.0:80 failed (98: Unknown error)Īnd the lsof command lsof -i -P -n | grep LISTEN Today, after I fire a regular update by using apt update, apt upgrade and a reboot, my web server is down. I have a server using Ubuntu Server 22.04 LTS with nginx and php supported for a long time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |