Scalix Forums

After a successfull install I went to Firefox browser and typed "http://192.168.1.45:8080/sac" & got "The connection was refused". I know Apache works with the default Apache page. I guessing the Scalix doesn't configure the whole shooting match for you. For Java I used "j2sdk1.4.2_08" & for Tomcat I used "jakarta-tomcat-5.5.9". I'm using Fedora core3 for an OS.

A Connection Refused message would indicate that tomcat isn't listening on port 8080.

However, we do not currently support tomcat 5.5.x with SAC or SWA. Please use the version of tomcat that is on the install media in the third_party directory.

Cheers

Dave

ScalixSupport wrote:A Connection Refused message would indicate that tomcat isn't listening on port 8080.

However, we do not currently support tomcat 5.5.x with SAC or SWA. Please use the version of tomcat that is on the install media in the third_party directory.

Cheers

Dave

If I knew the "third_party directory existed, I wouldn't have spent a half hour looking for tomcat on the internet! I don't know how to uninstall tomcat.

i would suggest that you run through the installer in uninstall mode, uninstalling the res, sac and swa components, leaving the server in place.

you then go to whereever you installed your tomcat home and remove the whole directory, e.g. rm -rf /opt/jakarta-tomcat-5.5.10/

then, restart the installer, go into custom mode, select the sac and swa components only and run through the install.

when the tomcat/java selection screen appears, hit the install button, select the third_party directory as source directory in the upcoming tomcat install screen and install under /opt as CATALINA_HOME.

that should hopefully do the trick!

Hi!

I got this same problem, post shutdown (i have scalix/redhat setup in vmware on my work laptop so shutdowns are unavoidable :) ).

Did some googling and searching these forums and it turned out to be simply that tomcat wasn't started. Used the Tomcat start script and problem solved....

My question is though, shouldn't Tomcat be starting by default and if it isn't does anyone have any suggestions why not?

Cool, hope you can help. Thanks for the rocking product!

you are absolutely right - and we listen.

the next version of scalix will have an improved installer that will
a) in a typical install situation always install the officially supported tomcat version under /opt/scalix-tomcat
b) create a proper init start script and set it to auto-start on both suse and redhat platforms
c) integrate tomcat with apache using the JK connector for improved stability and performance

hope this will make the kind of issue reported here obsolete once and forever! ;-)

We absolutely want to be the easiest and safest to install product of such kind on Linux; we want you to take care of the needs of your users, not figure out some strange dependency or missing package or stuff just not setup right! :-)

hope this helps,

-- Florian.

Sure does help :)

I just thought I had done something wrong (like quoting myself in a forum posting for example!).

Wicked, so I just need to modify init script to have Tomcat start on startup, that's ok I can do that.

As far as your goal of ease of setup, well, I'm sure you'll get there. I think the most important thing is having a solid scalable backend, which it seems you already have.

I know you are probably already considering it but I'd just like to make a plug for Debian support. If you support Debian stable I'm sure you will find a lot more admins will take a look at your product. One step at a time though I guess.

From all the postings I have read from Scalix support staff I must congratulate you on your professionalism and extremely helpful and prompt postings!