I was wondering if anyone else has tried to install this release yet. I verified that my MD5 checksum matches, but I sill am unable to install AES without several errors such as...

11:05:05 | [ 38] 224-httpd-2.2.15-29.el6_4.i686.rpm...
warning: /var/disk/Releases/7.0.0.0.0.13-0/subsys/ThirdParty/224-httpd-2.2.15-29.el6_4.i686.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
error: rpmdb: damaged header #2 retrieved -- skipping.
error: rpmdb: damaged header #2 retrieved -- skipping.
error: rpmdb: damaged header #2 retrieved -- skipping.
error: rpmdb: damaged header #2 retrieved -- skipping.
error: rpmdb: damaged header #2 retrieved -- skipping.
error: rpmdb: damaged header #2 retrieved -- skipping.

Log file attached

Where did you get the AEServices software from? The DevConnect portal or somewhere else. Just so I know what your starting point was.

I downloaded the file from DevConnect on Aug 25th.

By "the file" are you talking about the software only ISO file? What type of server are you installing this on? Is this a clean install or upgrade? I know AE Services 7.0 is going from RHEL 5 to 6.5. Did you update the Redhat Linux version to 6.5? What documentation are you following, and what page/step did you encounter the error?

Sorry for the lack of information...

I am using swonly-7.0.0.0.0.13-20150629.iso
MD5 Checksum: 67F5B343C2747D0328D3A5AE24A50028
SHA-1 Checksum: 567D86A3FF5B045FF1C919AF73AEF0C6B2D00CB0
SHA-256 Checksum: B56793B4661789582B06E3ACD840ED922BD5095F89411BECA7EA5071C4770CAD
SHA-512 Checksum: 4F79DF5DD0DB487E6BC6BAB509E25A646F4BFF1B742AB7D838BD8C7F272E4308B252D6575AABE060D17839E45F8BF8DAE27F750524671708A6CF04C82548042D

This is a new install on RHEL 6.5 32bit, on both a physical server and a VM image which meet the requirements as outlined in Deploying Avaya Aura® Application Enablement Services in a Software-Only Environment - Release 7.0 Issue 1 August 2015.

The installation completes, yet I am unable to access the AES Management webpage. My first observation was that I am unable to start the httpd service. After a complete reinstall I noticed that there were several messages logged in the AES installation log (attached in my initial post).

I have installed AES software-only regularly since version 3.0 and have never come across such an issue.

update...

I was able to resolve the "error: rpmdb: damaged header #2 retrieved -- skipping." errors by running "rpm --rebuilddb"

The next issue was when starting httpd i received "(2)No such file or directory: could not open mime types config file /etc/mime.types."
Two servers had different outcomes to this issue...
One I was able to copy /usr/share/cups/mime/mime.types to /etc and it was fine.
The other did not have this file anywhere. I needed to manually install mailcap to get mime.types. Oddly on this server, the cust account only had user management access.

At least I have one system up and running, I can start testing now.

Thanks,
Jeff

Just to make sure, did you follow all the sections in chapter 3 of the Deploy guide when you installed RHEL 6.5?

Yes, I did follow the Linux install section of the guide.

I'd also like to point out that in Chapter 3, point 6 the note suggests running /usr/bin/system-config-securitylevel-tui to disable SELinux. This command doesn't appear to exist any longer.

Also, in Chapter 4, point 5 the note indicates that you should update to Linux 5.8 rather than 6.5.

Okay, thank you for all of that information. I will take it to the developers.

The developers told me that your issues were encountered because of documentation errors. They are working on getting an updated version of the documentation out. Once they have posted the new version we will put it on the DevConnect portal.