Issue Details (XML | Word | Printable)

Key: GLASSFISH-16557
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: kshitiz_saxena
Reporter: Jothir Ganesan
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

Unable to start Apache2.2 64bit on Sparc after installing lb plugin

Created: 05/May/11 01:41 AM   Updated: 18/May/11 03:27 AM   Resolved: 18/May/11 03:27 AM
Component/s: load_balancer
Affects Version/s: 3.1.1
Fix Version/s: 3.1.1_b04

Time Tracking:
Not Specified

Environment:

Solaris Sparc 10 + Apache2.2 64bit + glassfish lb plugin 3.1.1 b01.


Tags:
Participants: Alex Pineda, Jothir Ganesan and kshitiz_saxena


 Description  « Hide

After installing loadbalancer plugin, when I try to start apache, the file
/usr/lib/libCstd.so.1 added to httpd.conf by lb plugin, is complained as 32bit.

I replaced it with /usr/lib/sparcv9/libCstd.so.1(which is 64bit), but now when I try to start, the error is:

httpd: Syntax error on line 412 of /space/gf-ha/64bit/apache2.2/conf/httpd.conf: Cannot load /space/gf-ha/64bit/apache2.2/modules/mod_loadbalancer.so into server: ld.so.1: httpd: fatal: libsasl.so: open failed: No such file or directory



Jothir Ganesan added a comment - 05/May/11 02:35 AM

The issue was fixed after relogging to the machine and restarting apache.


Jothir Ganesan added a comment - 05/May/11 03:35 AM

The fix of that file location should be done on the plugin installer.


Alex Pineda added a comment - 16/May/11 01:05 PM

Raising the priority of the bug to get resolution. Added [Blocker] to the bug synopsis for easier tracking.


kshitiz_saxena added a comment - 17/May/11 07:10 AM - edited

This issue is not blocker. Apache will work if you manually edit httpd.conf and update it as mentioned in description.

The second issue mentioned in description "httpd: Syntax error on line 412 ...." is not reproducible. That is why this issue was initially closed, and then reopened only for installer fix.


kshitiz_saxena added a comment - 18/May/11 03:27 AM

The latest loadbalancer-configurator will have this fix.