Upgrade to 4 isnt working

[hostingguy]

Following the upgrade instructions, it says to just run "aum -uf" and it will happen. Unfortunately that doesnt seem to work for me, is there something else I can do?
Additionally, is there a way to script this so I can run it across dozens of boxes with out having a manual human agree to install the DB and what not?

[root@server ~]# aum -uf
Checking for updates..
Upgrading ASL Components
Updating ASL Core: successful [OK]
Updating APPINV to 201402101531: updated [OK]
Updating CLAMAV to 201403151627: updated [OK]
Updating GEOMAP to 201403191134: updated [OK]
Updating MODSEC to 201403181244: updated [OK]
Updating Anti-Spam Protection: updated [OK]
Updating Attack Protection: updated [OK]
Updating Dataloss Protection: updated [OK]
Updating Malware Protection: updated [OK]
Updating Rootkit Protection: updated [OK]
Updating Shell Protection: updated [OK]
Updating OSSEC to 201403101910: updated [OK]
Updating Self Healing modules: updated [OK]
Updating Brute Force Protection: updated [OK]
Updating Rootkit Protection: updated [OK]
[root@server ~]# asl -v
ASL Version 3.2.18-37.el5.art: UNSUPPORTED: An update is available.
[root@server ~]# aum -uf
Checking for updates..
Upgrading ASL Components
Updating ASL Core: successful [OK]
Updating APPINV to 201402101531: updated [OK]
Updating CLAMAV to 201403151627: updated [OK]
Updating GEOMAP to 201403191134: updated [OK]
Updating MODSEC to 201403181244: updated [OK]
Updating Anti-Spam Protection: updated [OK]
Updating Attack Protection: updated [OK]
Updating Dataloss Protection: updated [OK]
Updating Malware Protection: updated [OK]
Updating Rootkit Protection: updated [OK]
Updating Shell Protection: updated [OK]
Updating OSSEC to 201403101910: updated [OK]
Updating Self Healing modules: updated [OK]
Updating Brute Force Protection: updated [OK]
Updating Rootkit Protection: updated [OK]
[root@server ~]# asl -v
ASL Version 3.2.18-37.el5.art: UNSUPPORTED: An update is available.

[mikeshinn]

Please see the upgrade instructions:

https://www.atomicorp.com/wiki/index.ph ... SL#ASL_4.0

[hostingguy]

Mike,

I followed those instructions, both from this line

If this is set to "all", ASL will automatically upgrade itself based on your upgrade configuration, which is by default to check for updates daily. You can change this to hourly if you wish the system to check more often, or you can force an upgrade by following the steps below.

as well as manually

# grep UPDATE_TYPE /etc/asl/config
UPDATE_TYPE="all"

yum upgrade mod_security tortix-waf

Loaded plugins: allowdowngrade, changelog, downloadonly, fastestmirror, protectbase, rhnplugin
Loading mirror speeds from cached hostfile
* asl-3.0: www5.atomicorp.com
* atomic: www5.atomicorp.com
* cloudlinux-x86_64-server-5: slc-proxy.cl-mirror.net
atomic | 1.9 kB 00:00
atomic/primary_db | 1.4 MB 00:00
Excluding Packages in global exclude list
Finished
Excluding Packages from Atomicorp - Atomic Secured Linux 3.0
Finished
Excluding Packages from CentOS / Red Hat Enterprise Linux 5 - atomicrocketturtle.com
Finished
Excluding Packages from Plesk Server Administrator
Finished
383 packages excluded due to repository protections
Setting up Upgrade Process
No Packages marked for Update

ran asl -f -s

[ ... left out for readability ... ]
Stopping psmon: [ OK ]
Starting psmon: [ OK ]

Generating Report: Complete

[root@server ~]# asl -v
ASL Version 3.2.18-37.el5.art: UNSUPPORTED: An update is available.

So I am unclear as to which step I missed as I was root user (step 1), update type is set to all (2), I ran aum -uf (3), manually ran YUM (4) and also ran asl -f -s and still nothing was updated, even though it should have been auto updated due to the update type.

[mikeshinn]

You're using the 3.2 upgrade method, that wont work to upgrade 3.2 to 4.0.

Please see the article, which I have cut and pasted below:

https://www.atomicorp.com/wiki/index.ph ... SL#ASL_4.0

ASL 4.0 uses the ASL installer to upgrade from 3.2 to 4.0. You can upgrade ASL by following these steps:

Step 1) Become the root user

As the root user, run step 2 below. Do not use "sudo" to run these commands.

Use this command to become root:

su -

Step 2) Run the installer

Cut and paste the command below, and run this command as root:

wget -q -O - https://www.atomicorp.com/installers/asl |sh

Follow the instructions in the installer being sure to answer the configuration questions appropriately for your system.

Note: You must have a version of wget installed that supports HTTPS to install ASL, as described on the ASL prerequisites page.

If you do not get any output from the installation command it is likely wget on your system was replaced with a crippled version that does not support SSL. Please see this article to test if your wget supports SSL if you are unsure:

https://www.atomicorp.com/wiki/index.ph ... sites#wget

Step 3) Reinstall the ASL database

During installation, when asked if you want to reinstall the ASL database, answer yes. ASL4 has a new database schema that is faster, and reinstallation of the database is required.

[hostingguy]

Ahh I see, I thought that was upgrade instructions for 3.2 users, and for a new 4.0 install run the installer ...
I'll give that a shot.

btw is there a way to do an unattended install, or bypass the human prompts so I can script this against multiple machines?

[imadsani]

Unattended installs have been introduced but I'm not sure whether they apply to updates

https://www.atomicorp.com/the-news/333-asl4.html

[hostingguy]

Yeah I saw that in the release, but I was hoping for some guidance on how to install it