October 26, 2008 at 17:50Ubuntu Linux Unpleasant Feature for System Administrators
Reorganize disk space to store information on a production server that is running Ubuntu Linux management, it has opened a very interesting feature: the directory / var / run is required to be on the root filesystem!
I assembled a RAID array, transferred / var to it, and entered the mount point. When the system started up, very strange things began to be observed: most of the daemons automatically stopped loading at startup, the network does not start (/ var / run / network is not created) and similar anomalies. At the same time, viewing logs does not give anything concrete.
Solution: create on the root FS ( /) directories / var / run (root: root, drwxr-xr-x) and / var / lock (root: root, drwxrwxrwt), which will give a normal start, and immediately after start / var located on the array will be correctly included in the system.
I assembled a RAID array, transferred / var to it, and entered the mount point. When the system started up, very strange things began to be observed: most of the daemons automatically stopped loading at startup, the network does not start (/ var / run / network is not created) and similar anomalies. At the same time, viewing logs does not give anything concrete.
Solution: create on the root FS ( /) directories / var / run (root: root, drwxr-xr-x) and / var / lock (root: root, drwxrwxrwt), which will give a normal start, and immediately after start / var located on the array will be correctly included in the system.