Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
blocks:server:tweaks [2019-03-26 12:34] admin Finalized 1st release |
blocks:server:tweaks [2023-03-14 20:58] (current) mattias [Removing Unifi Wifi Support] |
||
---|---|---|---|
Line 3: | Line 3: | ||
PIXILAB regularly revisits and improves the Linux server image, resulting in newer releases. The release is indicated by the date shown as part of the filename. However, for a running installation, | PIXILAB regularly revisits and improves the Linux server image, resulting in newer releases. The release is indicated by the date shown as part of the filename. However, for a running installation, | ||
+ | This article describes how to update server images based on Ubuntu 18. If you're using server image version 200525 or later, based on Ubuntu 20, most of what's described below is already been taken care of. However, you may still want to update your operating system from time to time to keep up-to-date with security patches. | ||
- | ===== Linux Operating Systemn Updates ===== | + | :!: If you're using an older version of server, based on Ubuntu 16, released before 2019-05-28, first follow [[blocks: |
+ | |||
+ | ===== Operating System Updates ===== | ||
System components are updated regularly. Most updates are not related to Blocks at all, and make no difference. But occasionally, | System components are updated regularly. Most updates are not related to Blocks at all, and make no difference. But occasionally, | ||
- | To update your server: | + | |
- | + | - Switch to the pixi-admin user (password is " | |
- | | + | |
- | - Switch to the pixi-admin user. | + | |
- Click the orange " | - Click the orange " | ||
- Select the " | - Select the " | ||
- If you see "OS updates", | - If you see "OS updates", | ||
- | - Other items may appear in the list (such as the " | + | - Restart |
- | {{ : | + | ===== Update Java ===== |
- | Finally, restart the server to make the updates take effect. | + | Blocks 4.1 and later uses a newer version of Java. If your server |
- | :!: While most updates are for the better (or at least neutral), they may occasionally cause problems. Make sure to test all important system functions after updating your server. | + | - Switch to the pixi-admin user. |
+ | - Open a terminal window using the terminal icon on the left hand side. | ||
+ | - Copy and paste the following commands into the terminal window: | ||
+ | < | ||
+ | sudo apt-get update | ||
+ | sudo apt-get install -y wget apt-transport-https | ||
+ | sudo wget -O - https:// | ||
+ | sudo echo "deb [signed-by=/ | ||
+ | sudo apt-get update | ||
+ | sudo apt-get install -y temurin-11-jdk | ||
+ | </ | ||
- | ===== Updating Blocks ===== | + | Enter the pixi-admin user's password when requested. Then switch to Java 11 using the following command: |
- | To update | + | < |
+ | sudo update-alternatives --config java | ||
+ | </ | ||
- | ===== Updating | + | When prompted, type the number corresponding to " |
- | The way the Blocks server | + | Finally, verify that Java 11 is now selected: |
- | - Download {{ : | + | < |
- | - Move the TAR file to your Linux Blocks server. | + | java -version |
- | - Double click the TAR file on the Linux server. | + | </ |
- | - Select both files and drag them to the home folder of the pixi-server user. | + | |
- | {{ : | + | The output should indicate " |
- | :!: To use these scripts to start and stop the server, you must be running Blocks 2.3 or later. | + | ==== Offline Procedure ==== |
- | Once installed, you can start and stop Blocks in either of the following ways: | + | If your Linux-based Blocks server doesn' |
- | | + | |
- | | + | - Doing so shows a list of files. If you receive an error message, |
- | | + | |
- | | + | |
+ | - On your Blocks server, log in as the pixi-admin user. | ||
+ | | ||
- | The advantage with the last option is that you can start/stop the server without using the GUI. This is often useful when accessing the server remotely, e.g. over a VPN connection or similar. | + | < |
+ | sudo apt install | ||
+ | </code> | ||
- | :!: No Blocks window will appear on screen when started from a non-GUI session, such as over SSH. You can check whether | + | Make sure there' |
- | ===== Reducing the Wear on the SSD ===== | + | ===== Updating Blocks |
- | During normal operation of Blocks, most disk accesses will be READ operations used to serve media and other data to the display spots. However, due to the default behavior of most Unix-based operating systems, such accesses may still incur a write operation to update the "last accessed" | + | To update the Blocks |
- | + | ||
- | Fortunately, | + | |
- | + | ||
- | {{ :blocks: | + | |
- | + | ||
- | Click the //Disks// icon, opening a window like the one shown below. Click the large center partition of the disk to select it. Then choose "Edit Mount Options…" | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | At the beginning of the "mount options" | + | |
- | + | ||
- | < | + | |
- | noatime, | + | |
- | </ | + | |
- | + | ||
- | :!: IMPORTANT: Note that there must be a comma separating the word //noatime// from the word //errors// that was already there. | + | |
- | The result will look like this screenshot. | ||
- | {{ : | ||
- | Click OK to save your changes, then restart the server to make your changes take effect. |