Default OS clarity

[landNull]

Hi,

Thank you all for your hard work on BOA.

I need some clarity on the OS to use for the initial install.

In the <>Code github README.txt it says

"
@=> SUPPORTED OPERATING SYSTEMS -- please read also: docs/CAVEATS.txt

Devuan @ https://www.devuan.org/os/releases

• Devuan Chimaera (fully supported and the only OS version recommended)
  "

In the docs/INSTALL.txt it says

"

• Since Debian is running systemd, it should be removed before installing BOA,
  which involves procedure in five steps, as outlined further below.

&

4. Remove systemd in five steps:

   S1. Run 'boa init' command -- it will install sysvinit.
   S2. Reboot the server.
   S3. Run 'boa init' again so it can remove systemd.
   S4. Reboot the server again.
   S5. Run boa standard install command, as outlined below.
   "

I'm installing on a VPS that can only provide Debian installs.
So I had them do a fresh install of Debian Bullseye.

Q: Do I migrate the clean Bullseye to Devuan then run install
OR
Do I just follow the 5 steps in Step 4 and it is all good to go?

[omega8cc]

Good question. BOA requires that you first install it using the multi-step procedure on Debian. Only then you can upgrade it to Devuan, or just stay on Debian, although it’s not recommended.

_{Sent with GitHawk}

[omega8cc]

We could perhaps add the procedure to upgrade Debian to Devuan before actually installing BOA. It would also make the migration to Devuan slightly faster.

_{Sent with GitHawk}

[landNull]

We could perhaps add the procedure to upgrade Debian to Devuan before actually installing BOA. It would also make the migration to Devuan slightly faster.

Sent with GitHawk

It worked-ish!!! #1788 (comment)

[omega8cc]

Wow! Great illustration of all the hard work BOA is doing for you when used as intended. All the magic included is a result of countless hours of tedious testing, failing and debugging.

_{Sent with GitHawk}

[landNull]

Wow! Great illustration of all the hard work BOA is doing for you when used as intended. All the magic included is a result of countless hours of tedious testing, failing and debugging.

Sent with GitHawk

No doubt!
I have an opportunity to try the "Devuan first" method including boa init this time I will report back with my final breakdown.

[landNull]

First things first BOA is badass!!!

"Devuan first" method worked...ish!!! ;)

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WARNING
This is NOT a recommended install method
In the end I did this out of shear curiosity and
in the hopes of providing some insight to the devs
in case they chose to provide a "Devuan first" install
at some point.
ZERO SUPPORT GIVEN IF U DECIDE TO TRY THIS
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I was not expecting this outcome.

I simply had another opportunity to test one last variation I had not tried yet on a "Devuan first" BOA install figuring I might dig up more info for devs and to satisfy my curiosity.

The Breakdown

• Fresh install of Debian Bullseye on VPS
• Login using password provided by host
• Change password
• passwd
• Prep Work I did on my VPS
• sudo nano /etc/hostname
• delete hostname
• crtl x
• y
• reboot
• ssh-copy-id -i ~/.ssh/id_rsa.pub root@ip.add.re.ss -p customPort#
• ssh root@ip.add.re.ss -p custom port
• apt remove --purge apache2
• rm -rf /etc/nginx /etc/apache2 /etc/mysql
• Migrate Debian to Devuan using instructions from https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera
• boa init

ERROR!

BOA [18:01:24] ==> MODE: NORMAL INIT
BOA [18:01:24] ==> FATAL ERROR: You must define also _EASY_HOSTNAME

ATTEMPTED to troubleshoot via various iterations of the error

1. Full error
2. Removed timestamp
3. No insight was gained.

• reboot
• ssh root@ip.add.re.ss -p custom port
• screen
• boa in-lite public server.mydomain.org my@email o1 none php-min
• Installer runs

UPDATE
This glitch has nothing to do with BOA it is specific to a weird connection timeout issue I'm experiencing with my remote connection. I was able to confirm this after I processed a "Debian first" install as it stopped printing to the screen at the same exact point.

GLITCH

The script stopped outputting updates on the install to the terminal screen
Looking at the install log shows install stopped out put to the log after printing

Waiting for MySQLD graceful shutdown...to the screen or logs
MySQLD stopped
Removing locks...
MySQLD stop procedure completed
Creating locks...
Starting MySQLD again...
Waiting for MySQLD graceful start...
MySQLD started
Removing locks...
MySQLD start procedure completed

• After waiting for 30 minutes with no futher output
• Tested to make sure the server was still running
• Viewd htop everything looked good
• su -s /bin/bash aegir
• drush @hostmaster verify
• All good
• drush @hostmaster uli
• loaded uli in browser
• no ssl cert warning
• accept risks
• Initial login page loads everything is working great
• apt update
• To confirm I not hallucinating

OUTPUT

Get:1 http://repo.percona.com/percona/apt bullseye InRelease [9899 B]
Get:2 http://repo.percona.com/percona/apt bullseye/main Sources [4308 B]
Get:3 http://repo.percona.com/percona/apt bullseye/main amd64 Packages [17.6 kB]
Get:4 http://deb.devuan.org/merged chimaera InRelease [33.5 kB]
Get:5 http://deb.devuan.org/merged chimaera-updates InRelease [26.1 kB]
Get:6 http://deb.devuan.org/merged chimaera-security InRelease [26.4 kB]
Get:7 http://deb.devuan.org/merged chimaera/main Sources [8604 kB]
Get:8 http://deb.devuan.org/merged chimaera/main amd64 Packages [8312 kB]
Get:9 http://deb.devuan.org/merged chimaera/main Translation-en [6479 kB]
Get:10 http://deb.devuan.org/merged chimaera-updates/main Sources [8164 B]
Get:11 http://deb.devuan.org/merged chimaera-updates/main amd64 Packages [17.9 kB]
Get:12 http://deb.devuan.org/merged chimaera-updates/main Translation-en [11.2 kB]
Get:13 http://deb.devuan.org/merged chimaera-security/main Sources [159 kB]
Get:14 http://deb.devuan.org/merged chimaera-security/main amd64 Packages [276 kB]
Get:15 http://deb.devuan.org/merged chimaera-security/main Translation-en [191 kB]

• I watching the install log throughout the whole install
• tail -f /var/backups/barracuda-install-DATE-TIME.log
• No errors printed to the log, but the script stopped printing to the screen, and logs.

CONCLUSION

• No matter how you approach the install "Debian first" or "Devuan first" BOA installer is badass!!
• I did this mostly out of curiosity
• Definitely not the result I expected
  UPDATE
  I have been able to determine the issue with the logs and script not printing to the screen after the database restart is specific to my remote connection.
  _- I was not disconnected from the remote access at anytime during the install and the syslog show no errors
• I wish it had printed all of the output to the log as I would have something more to offer the devs :(_
• I hope my sucessflish ;) experiment is helpful in some way.

[omega8cc]

It’s exciting to see you willing to experiment and share the results with others, how refreshing attitude, thank you!

[landNull]

It’s exciting to see you willing to experiment and share the results with others, how refreshing attitude, thank you!

You're very welcome! Right back at you! 😄

[landNull]

UPDATE
In the end the only error I experienced with the "Devuan first" install is after running boa init on a fresh Devuan migration.

BOA [18:01:24] ==> MODE: NORMAL INIT
BOA [18:01:24] ==> FATAL ERROR: You must define also _EASY_HOSTNAME

The only issue is the _EASY_HOSTNAME variable not populating on Devuan. I have no idea if this is a small thing to address or not.

This glitch with the script and install log not printing output after the database restart has nothing to do with the BOA script it is specific to a weird connection timeout issue I'm experiencing with my remote connection.

I was able to confirm this after I processed a "Debian first" install as it stopped printing to the screen at the same exact point.

Yet in a previous "Debian first" install (#LearningCurve) everything worked as advertised.