Run servoy server on CentOS 5.0

Classic Servoy
1

I am missing something really simple here (I hope).
I built servoy 3.5.6 on an ubuntu worsktation, so I could run the GUI install.
I then copied the entire /usr/local/servoy dir tree to the remote server I need to run it on (which doesnt have a GUI). Its running CentOS 5.0. I start the sybase DB without any errors.
I start servoy_server.sh without any errors BUT servoy is NOT present on http://server:8080/ on the remote server. Checking the server.log file I see:

Picked up _JAVA_OPTIONS: -Xms64m -Xmx128m
0 [main] INFO com.servoy.j2db.util.Debug - Loading servoy.properties from /usr/local/servoy/servoy.properties
489 [main] INFO com.servoy.j2db.util.Debug - Loading - Done

…which looks good to me. But it seems that the internal tomcat does NOT start up. IF I try to telnet to server IP on port 8080 I get connection refused…if I try this on the ubuntu WS I built it on I get a connect so there is clearly some difference here.

Any tips/suggestions as to why the built in tomcat would not start without showing any errors?

NB I dont have any access to the remote server I need to install too except ssh/ftp/web.
Thanks
Al

2

Al,

Are there any other log files with some errors (servoy_log.txt perhaps?)

Have you tried telnet localhost 8080 from the centos machine itself?

Rob

3

Also verify that sybase is actually running when you attempt to start Servoy. You should se a process like “dbsvr10”

4

CentOS & RedHat by default will put the hostname when the system is configured on the line with the ‘localhost.localdomain’ entry.

Unfortunately, if you’re trying to use a service listening on an ethernet interface instead of the loopback address, it won’t work. I run into this all the time when configuring network services like Sybase ASE etc.

i.e. if my computer name is ‘jones’ and my eth0 is 10.0.0.5. then I need to make sure I’ve got a separate entry in /etc/hosts with jones and 10.0.0.5 from the 127.0.0.1 entry for localhost.

If you do end up making the change, either restart or do a ‘service network restart’ and then a netstat -an to see what ports your services are listening on.

HTH, Tony