Connector error with CF8 and RedHat6
Hi,
I have a virutal server, RedHat Enterprise 6, SELinux enforcing, that was cloned from a (working) dev box. CF and Apache both seem to be running fine; CF and HTML pages are both being served, I can get to the CF Administrator and do everything I normally do there. However, when I try to stop CF, I get an error saying:
Stopping coldfusion server.could not stop server, either it's not running, you don't have permission to stop
the server or it needs to be killed manually
The ColdFusion 8 server seems to be hanging, will stop non-gracefully
ColdFusion 8 has been stopped
I've got the right sudo privileges, so that isn't it. CF does eventually stop after a few seconds. When I try to start CF, I get the following:
Starting ColdFusion 8...
The ColdFusion 8 server is starting up and will be available shortly.
======================================================================
Running the ColdFusion 8 connector wizard
======================================================================
Configuring the web server connector (Launched on the first run of the ColdFusion 8 start script)
Running apache connector wizard...
ColdFusion 8 not started, will retry connector 12 more time(s)
ColdFusion 8 not started, will retry connector 11 more time(s)
...
(after the 12 more attempts)
The connector wizard has not been able to contact the local ColdFusion 8, connector installation aborted.
======================================================================
ColdFusion 8 has been started.
ColdFusion 8 will write logs to /opt/jrun4/logs/cfserver.log
======================================================================
When I check the connector install log, I have:
Macromedia JRun 4.0 (Build 108673)
os.name: Linux
os.version: 2.6.32-220.17.1.el6.x86_64
os.arch: amd64
platform: intel-linux64
Found port 2930 on host localhost
could not connect to port 2930 on host 127.0.0.1
javax.naming.ServiceUnavailableException: The connection to the remote JNDI server on host 127.0.0.1 at
port 2930 has failed (as have all backup hosts listed, if any) - please verify that the server is runn
ing and the NamingService is available [Root exception is java.net.NoRouteToHostException: No route to
host]
at jrun.naming.JRunNamingContext.connectToNameServer(JRunNamingContext.java:1349)
at jrun.naming.JRunNamingContext.getRemoteContextProxy(JRunNamingContext.java:1315)
at jrun.naming.JRunNamingContext.getContextProxy(JRunNamingContext.java:1135)
at jrun.naming.JRunNamingContext.lookup(JRunNamingContext.java:517)
at jrun.naming.JRunNamingContext.lookup(JRunNamingContext.java:495)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at jrunx.connectorinstaller.CIJndi.findServers(CIJndi.java:362)
at jrunx.connectorinstaller.CIJndi.<init>(CIJndi.java:141)
at jrunx.connectorinstaller.CIJndi.<init>(CIJndi.java:147)
at jrunx.connectorinstaller.ConnectorInstaller.parseArgs(ConnectorInstaller.java:228)
at jrunx.connectorinstaller.ConnectorInstaller.<init>(ConnectorInstaller.java:56)
at jrunx.connectorinstaller.ConnectorInstaller.main(ConnectorInstaller.java:760)
Caused by: java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:180)
at jrun.naming.JRunNamingContext.connectToNameServer(JRunNamingContext.java:1345)
... 11 more
Could not connect to any JRun/ColdFusion servers on host localhost.
Possible causes:
o Server not running
-Start Macromedia JRun4 or ColdFusion 8 server
o Server running
-JNDI listen port in jndi.properties blocked by TCP/IP filtering or firewall
on server
-host restriction in security.properties blocking communication with server
The system administrators here swear up and down that the firewall does not block connections from localhost, and that this machine is absolutely identical to the machine it was cloned from (which does not have this error). I have tried reinstalling CF on this machine, with the same result, except that if I reinstall, CF doesn't serve pages and I can't get to the Administrator. Same error messages in the connector log files, though. I am completely at a loss, and somewhat hesitant to sign off on a production server where the main application server won't start cleanly (and where it seems the connector can't run successfully; if nothing else, that seems like it would cause problems down the road when we go to upgrade to CF 10). If anyone has any suggestions for anything else I can try, I would greatly appreciate it.
Thanks in advance for any help!
~ Amanda
AdChoices