diff options
| -rw-r--r-- | issues/systems/tux04-production.gmi | 4 | ||||
| -rw-r--r-- | topics/deploy/machines.gmi | 2 | ||||
| -rw-r--r-- | topics/systems/mariadb/mariadb.gmi | 2 | ||||
| -rw-r--r-- | topics/systems/update-production-checklist.gmi | 47 |
4 files changed, 54 insertions, 1 deletions
diff --git a/issues/systems/tux04-production.gmi b/issues/systems/tux04-production.gmi index 01e1638..58ff8c1 100644 --- a/issues/systems/tux04-production.gmi +++ b/issues/systems/tux04-production.gmi @@ -6,6 +6,10 @@ Lately we have been running production on tux04. Unfortunately Debian got broken and that is alarming. We might as well try an upgrade. I created a new partition on /dev/sda4 using debootstrap. +The hardware RAID has proven unreliable on this machine (and perhaps others). + +We added a drive on a PCIe raiser outside the RAID. Use this for bulk data copying. We still bootstrap from the RAID. + Luckily not too much is running on this machine and if we mount things again, most should work. # Tasks diff --git a/topics/deploy/machines.gmi b/topics/deploy/machines.gmi index d3ae8d5..a7c197c 100644 --- a/topics/deploy/machines.gmi +++ b/topics/deploy/machines.gmi @@ -6,7 +6,7 @@ - [X] lambda01 172.23.18.212 (7c:c2:55:11:9c:ac) - currently 172.23.17.41 - [X] tux03i 172.23.17.181 (00:0a:f7:c1:00:8d) - 10 Gbs [X] tux03 128.169.5.101 (00:0a:f7:c1:00:8b) - 1 Gbs -- [ ] tux04i 172.23.17.170 (14:23:f2:4f:e6:10) +- [X] tux04i 172.23.17.170 (14:23:f2:4f:e6:10) - [X] tux04 128.169.5.119 (14:23:f2:4f:e6:11) - [X] tux05 172.23.18.129 (14:23:f2:4f:35:00) - [X] tux06 172.23.17.188 (14:23:f2:4e:29:10) diff --git a/topics/systems/mariadb/mariadb.gmi b/topics/systems/mariadb/mariadb.gmi index 7db78d1..ec8b739 100644 --- a/topics/systems/mariadb/mariadb.gmi +++ b/topics/systems/mariadb/mariadb.gmi @@ -16,6 +16,8 @@ To install Mariadb (as a container) see below and Start the client and: ``` +mysql +show databases MariaDB [db_webqtl]> show binary logs; +-----------------------+-----------+ | Log_name | File_size | diff --git a/topics/systems/update-production-checklist.gmi b/topics/systems/update-production-checklist.gmi index 2a1d520..553e479 100644 --- a/topics/systems/update-production-checklist.gmi +++ b/topics/systems/update-production-checklist.gmi @@ -3,6 +3,8 @@ # Tasks +* [ ] Install underlying Debian +* [ ] Get guix going * [ ] Check database * [ ] Check gemma working * [ ] Check global search @@ -16,9 +18,54 @@ The following are at the system level * [ ] Update certificates in CRON * [ ] Run trim in CRON +# Install underlying Debian + +For our production systems we use Debian as a base install. Once installed: + +* [ ] set up git in /etc and limit permissions to root user +* [ ] add ttyS0 support for grub and kernel - so out-of-band works +* [ ] start ssh server and configure not to use with passwords +* [ ] start nginx and check external networking +* [ ] set up E-mail routing + +It may help to mount the old root if you have it. Now it is on + +``` +mount /dev/sdd2 /mnt/old-root/ +``` + +# Get Guix going + +We can bootstrap with the Debian guix package. Next move the store to a large partion and hard mount it in /etc/fstab with + +``` +/export2/gnu /gnu none defaults,bind 0 0 +``` + +Run guix pull + +``` +wrk@tux04:~$ guix pull -p ~/opt/guix-pull --url=https://codeberg.org/guix/guix-mirror.git +``` + +Use that to install guix in /usr/local/guix-profiles + +``` +guix package -i guix -p /usr/local/guix-profiles/guix +``` + +and update the daemon in systemd accordingly. After that I tend to remove /usr/bin/guix # Check database +Basically recover the database from a backup is the best start and set permissions. We usually take the default mariadb unless production is already on a newer version - so we move to guix deployment. + +On tux02 mariadb-10.5.8 is running. On Debian it is now 10.11.11-0+deb12u1, so we should be good. On Guix is 10.10 at this point. + +``` +apt-get install mariadb-server +``` + => topics/systems/mariadb/mariadb.gmi # Check sending E-mails |