Earlier today I copied data from the old server (supernews) to the new server (x8dtu). Now that the database has the correct information regarding when reports were last sent out, we can begin to enable those reports. The work has already been done to move the reports from cronjobs into periodic scripts. For our purposes, […]
Enabling report notifications on the new server Read More »
Ever since the new server went into production, sometime in 2017, the notification emails, which tell you what has changed, have been coming from the old server. I never did that changeover. The old server was still processing incoming commits, so the notifications were accurate. However, new accounts would not get notifications and changes to
Moving the email notifications to the new server Read More »
When the website enters maintenance mode, there are a few steps to ensure the database is not updated while we dump the data, but still allow the website to display pages. Disable ingress commit processing In the ingress host (for example, x8dtu-ingress01), stop the FreshPorts daemon: [dan@x8dtu-ingress01:~] $ sudo svc -d /var/service/freshports/ [dan@x8dtu-ingress01:~] $ Ensure
Upgrading the database Read More »
x8dtu contains two jails for database servers: x8dtu-pg01 and x8dtu-pg02. At any given time, one is the production database server, and contains the IP address 127.1.54.32. Let’s assume x8dtu-pg02 is on PostgreSQL 10.6 and we are upgrading to PostgreSQL 11.1 on x8dtu-pg01 The new packages would be installed on x8dtu-pg01. pg_dump would be run on
Moving the production database server IP address Read More »
This procedure is rarely used, but is documented nonetheless. A database server change is usually accomplished by moving the IP address from one server to another, not by adjusting the clients. The production database server is usually at 127.1.54.32. When changing from one database server to another, there are a few configuration files to update:
Swapping database servers Read More »