Re-installation – a second time
Made a mistake in re-installation: set the system up as a cluster member, added the wrong data (cluster password) so Iris didn’t start – hung on joining the cluster – obviously. So I re-installed VMS again from scratch (INIT), now without clustering to begin with, and configured TCPIP. Now the problems with FTP were gone.
Next, I copied the saved general directory that contains all startup files (amongst other things) and the system-specific files that call these local procedures, being sure I covered all that is installed (and bypassing everything that isn’t yet) and rebooted. It didn’t work- because the queue manager needed to be defined and started, and queues defined. Once that was done, reboot went fine – as expected – except that, once again, FTP was said to be started in the log, but the server process (TCPIP$FTP_1) was still missing. So I moved startup of TCPIP from the local procedure (started on queue SYS$STARTUP) to SYSTARTUP_VMS.COM (which is started by the STARTUP process), and now FTP (and other services that failed to start) now do run.
But in the process I encountered something weird.
Previously, on startup, the EFI startup procedure would add CPU’s 1,2 and 3 to join the pool. CPU #0 is the startup-processor (Monarch). Now, it’s just CPU #1 that is added. is that the second code on the first CPU – or the first on the second CPU? EFI shell cpuconfig shows me 2 CPU’s running and active – and when trying to enable hyperthreading, the system responds that the CPU’s don’t support it.. So one CPU must be down… Something to dive into…
Anyway: I can now access the system using FTP so I can move all software that is needed, onto the system. and re-install compilers and development environments
NASTY!!!! MariaDB keeps causing problems…Lost connection again…