I have tried both a CentOS installation in VMVare Fusion, and now an official CentOS instance on AWS, and I get about the same problem: I can't connect to Lasso throguh Apache, I just get 500 Internal Errors.
I grabbed the CentOS 6 -x86_64- - with Updates-6 - 2013-05-27-AutogenByAWSMP instance from the Marketplace and fired it up in EC2. I'm a n00b both with CentOS and AWS but have had some help. I managed to fix the incorrect security context the Apache Lasso Connector was installed with, and now Apache starts fine. Lasso is running:
[root@ip-172-31-7-45 ~]# ps ax | grep lasso
1262 pts/0 S 0:00 sudo -u lasso env LD_LIBRARY_PATH=/usr/lib/jvm/jre/lib/amd64:/usr/lib/jvm/jre/lib/amd64/server:/usr/lib/jvm/jre/lib/i386:/usr/lib/jvm/jre/lib/i386/server ./Lasso8Service
1273 pts/0 Sl 0:03 ./Lasso8Service --nolisten --ischild --siteid=1 --sitename=default --pipename=lassosite_8.6_1 --workingdir=LassoSites/default-1
1365 pts/0 S+ 0:00 grep lasso

I installed Lasso 8.6 with Yum, and to me the lasso8.conf and the Lasso connector look fine.

But, accessing any lasso page, including http://ec2-54-194-109-92.eu-west-1.compute.amazonaws.com/ServerAdmin.LassoApp
just yields a 500 Internal Server Error. To me it looks like Apache can not connect to Lasso, but I am at a loss to understand why. I can't se anything in the Apache logs (apart from the 500 error) and if I start Lasso in console mode it doesn't seem to get any input that I can see from Apache when I for instance try to load the above ServerAdmin.

Can anybody offer any suggestions to how I can proceed to debug this? I did get it to work for a while on the VMVare Fusion CentOS installation, but only if I manually made sure Lasso started after Apache. But now I can't get it to work any which way I try.

Lars

#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>