Error during install of 11-Sourceguardian

[mocjack]

Running CentOS 64 bit. Paths have all been corrected per earlier posts on fixing 64bit issues. When I get to the part where I install component 11 - Sourceguardian I am getting the following errors:

---
[root@gnagios1 nagiosxi]# ./11-sourceguardian
Archive: sourceguardian/ixed4.lin.x86-64.zip
inflating: /usr/lib64/php/modules/ixed.4.3.lin
inflating: /usr/lib64/php/modules/ixed.4.3ts.lin
inflating: /usr/lib64/php/modules/ixed.4.4.lin
inflating: /usr/lib64/php/modules/ixed.4.4ts.lin
inflating: /usr/lib64/php/modules/ixed.5.0.0.lin
inflating: /usr/lib64/php/modules/ixed.5.0.0ts.lin
inflating: /usr/lib64/php/modules/ixed.5.0.1.lin
inflating: /usr/lib64/php/modules/ixed.5.0.1ts.lin
inflating: /usr/lib64/php/modules/ixed.5.0.2.lin
inflating: /usr/lib64/php/modules/ixed.5.0.2ts.lin
inflating: /usr/lib64/php/modules/ixed.5.0.lin
inflating: /usr/lib64/php/modules/ixed.5.0ts.lin
inflating: /usr/lib64/php/modules/ixed.5.1.lin
inflating: /usr/lib64/php/modules/ixed.5.1ts.lin
inflating: /usr/lib64/php/modules/ixed.5.2.lin
inflating: /usr/lib64/php/modules/ixed.5.2ts.lin
inflating: /usr/lib64/php/modules/ixed.5.3.lin
inflating: /usr/lib64/php/modules/ixed.5.3ts.lin
Sourceguardian extension found for PHP version 5.1
Adding Sourceguardian extension to php.ini
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Stopping httpd: [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
[FAILED]
Installed SourceGuardian loaders
[root@gnagios1 nagiosxi]# ls
---

Can anyone assist? Obviously there is something else using port 80 and this is stopping my progress but what are the other issues and how do I proceed from here?

Thanks to anyone in advance!

-mocjack

[mocjack]

Also attached logs so far.... just in case it helps to diagnose.

[tonyyarusso]

Oddly enough, I think this is actually okay. I believe I've run into the same message, and it turned out to just be two things trying to happen at once, which corrected itself later in the install. I'm reworking the install scripts a bit currently, which hopefully will alleviate some of these issues.