Phrases: yeah, true... I'll meet you halfway by adding "knowingly, consciously or by explicit intent", OK?
When did you upgrade?: Indications (file timestamps in places like /etc and /usr/bin on the new server, my last backup of the previous server, and some file/directory timestamps on the old server) are that I performed the upgrade over May 30th to May 31st 2022.
How...I backed up my old server (9.2, "spencer") and performed a fresh install of Koozali 10 on a different computer ("dejavu") with new drives.
As the new machine is explicitly a mail server, I would have restored user files (Maildir) from /home/e-smith/files/users
somehow. I'll address that part in a sec...
Interruption: The new server has been operating since the install, so the basic install was obviously successful. The file restore opens up a question, though:... As I said in a previous post in this thread, the location that I created on my backup NAS for the new server is completely empty of backup files, so I obviously hadn't set up backups. When I tried to run a backup manually yesterday, I found that I couldn't mount the nfs drive, because nfs-utils wasn't installed. The lack of any backup data for dejavu, plus the absence of nfs-utils tells me that I couldn't have set up backups, although that would have been important to me. That's what I mean by "interrupted".
BUT somehow the Maildir contents for all the users
was migrated to the new server, because we all have our old mail. There are three ways I know I could have done that:
1. via a tar restore;
2. by mapping the /home/e-smith/files/users directory as an nfs share into the new machine, and copying the files that way. The "exports" file on the old server is empty, and dated Jan 12 2010, so I cannot have moved files that way. /etc/samba/smb.conf is dated 31st May 2022, so i may have transferred
some file that way, but the only shares in smb.conf are in ibays, which is not where Maildirs are located.
3. By setting up imap accounts for each of my users on both the old and new servers on my email client, and using that to copy all the mail files from one account to the old server to the corresponding account on the new server. Because I only needed to transfer mail, that's probably the method I used.
"
What happened between these two?" Nothing, to my knowledge: as I said, there's nothing that I would have done myself. And there is absolutely no reason for me to have removed the e-smith-backup module. I didn't even know about that module at that time, and while, because of work stress at the time (new job) I may have forgotten to set up backups, the chances of my having inadvertently removed the very module responsible for doing it are beyond improbable. And to remove nfs as well? Something that I knew perfectly well that I would need for backups? That is simply outside the realms of plausibility. No, I insist that I did not remove those modules myself.
"
Prior to June 5th" Well that's this year... I wouldn't have been doing anything with the server at that time: I was preparing for a business visit to my head office around that time, and I left town June 4th for a week.
Here's an extract from the update log around June 5th...
/var/log/yum/yum-update.log-20230524:May 24 00:19:43 dejavu yum_update_dbs: Existing lock /var/run/yum.pid: another copy is running as pid 3488.
/var/log/yum/yum-update.log-20230524:May 24 00:19:43 dejavu yum_update_dbs: Another app is currently holding the yum lock; waiting for it to exit...
/var/log/yum/yum-update.log-20230524:May 24 00:19:43 dejavu yum_update_dbs: The other application is: yum
/var/log/yum/yum-update.log-20230524:May 24 00:19:43 dejavu yum_update_dbs: Memory : 112 M RSS (1.4 GB VSZ)
/var/log/yum/yum-update.log-20230524:May 24 00:19:43 dejavu yum_update_dbs: Started: Wed May 24 00:18:50 2023 - 00:53 ago
/var/log/yum/yum-update.log-20230524:May 24 00:19:43 dejavu yum_update_dbs: State : Uninterruptible, pid: 3488
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x251: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x253: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x262: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x264: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x265: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x266: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x267: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x268: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x269: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x26a: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x26b: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x26c: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x26d: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x26e: 32495/140502041245504
/var/log/yum/yum-update.log-20230606:Jun 5 03:47:20 dejavu yum_update_dbs: BDB2053 Freeing read locks for locker 0x26f: 32495/140502041245504
/var/log/yum/yum.log.1687183069:Warning: RPMDB altered outside of yum.
/var/log/yum/yum.log.1687183069:Reload yum db for server-manager
/var/log/yum/yum-update.log-20230619:Jun 19 08:59:21 dejavu yum_update_dbs: Existing lock /var/run/yum.pid: another copy is running as pid 27150.
/var/log/yum/yum-update.log-20230619:Jun 19 08:59:21 dejavu yum_update_dbs: Another app is currently holding the yum lock; waiting for it to exit...
As if that wasn't bad enough, I see this excerpt from yesterday in /var/log/messages...
Jul 10 01:00:01 dejavu su: (to qmailr) root on none
Jul 10 01:04:17 dejavu kernel: [860305.626185] cvm-unix[32656]: segfault at 0 ip 00007f7c015b3037 sp 00007ffeb5b4a578 error 4 in libc-2.17.so[7f7c01474000+1c4000]
Jul 10 01:04:17 dejavu kernel: cvm-unix[32656]: segfault at 0 ip 00007f7c015b3037 sp 00007ffeb5b4a578 error 4 in libc-2.17.so[7f7c01474000+1c4000]
Jul 10 01:05:01 dejavu su: (to qmailr) root on none
Jul 10 01:10:01 dejavu su: (to qmailr) root on none
Jul 10 01:15:01 dejavu su: (to qmailr) root on none
I'm wondering if, at this point, I shouldn't just do a fresh install..
19 Replies
1311 Views