In the meantime (prior to the restart having completed), the server's handing out Error 500's like this:

Server Error

The server encountered an internal error and was unable to complete your request.

Could not connect to JRun Server.

So, I check /opt/coldfusion9/bin/coldfusion status and it tells me:

Could not contact the ColdFusion Application Server running on this machine:

Perhaps ColdFusion is not running on this machine?

Perhaps cfstat is not enabled from the ColdFusion administrator?

Perhaps ColdFusion was not restarted after enabling cfstat?

Perhaps cfstat service is not listening on default port?

Use option -port with port number as per the cfstatport

defined in the neo-metrics xml file.

Erm. Funny that that status script could contact the CAS because when I ran `top`, I could see it using up CPU and RAM, and a `ps aux` revealed it was, in fact, running...maybe it was just still starting up and wasn't ready to "talk". I'm not sure.

Obviously, I'm curious as to what the cause was in the first place...cfserver.log just before the `autorestart` isn't telling me much, so I tail the application.log and the exception log but there's nothing in there with a timestamp right before this mysterious autorestart.

This is weird too: I can't actually seem to stop the CF server from running:

Here, I get tired of waiting and hit Ctrl-C, but sometimes I'll wait and wait and it never does anything other than draw dots.

root@coffeereview:~# /opt/coldfusion9/bin/coldfusion status

Pg/Sec DB/Sec CP/Sec Reqs Reqs Reqs AvgQ AvgReq AvgDB Bytes Bytes

Now Hi Now Hi Now Hi Q'ed Run'g TO'ed Time Time Time In/Sec Out/Sec

0 0 0 0 -1 -1 0 0 0 0 -11525740 0 0

Still running. Obviously, I could hit the PID with a kill -9, but that seems a lottle rough, and not the ideal way to go about it. Last time I force quit it that way, I think it took even longer than 10 minutes to start back up when I ran `service coldfusion9 start`.

166 Views and 0 replies after 3 days. No one wants to give this one a go, eh? ;-) Why not?

Anyway, I've had a brief respite in the WebSitePulse alerts. Upgrading to an M1.Medium EC2 instance may or may not have been what stopped the daily crashes (double the RAM and CPU of the M1.Small). Are there official system requirements for CF that I should have been aware of before attempting to run it on an M1.Small?

In any case, I'm apprehensive about trying a restart because of the other issues I reported (which I've now posted in other threads:

These last two sub-issues have been resolved. Apparently, both my inability to stop the server and the extremely long startup time were caused by not having my internal IP in my /etc/hosts file. Adding a listing like so fixed the problem:

10.176.195.20 servername.com servername

From my ifconfig:

inet addr:10.176.195.20 Bcast:10.176.195.255 Mask:255.255.254.0

Previously, there had been no entry in /etc/hosts for 10.176.195.20.

The other issue, that of frequent mysterious restarts, seems (perhaps) to have been resolved by upgrading the resources on the EC2 instance. However, the M1.Small met the system requirements for CF9, so that shouldn't have been necessary and it might have been code changes I made which require many fewer calls to MySQL. I'm actually planning to downgrade the server (back to what it was before) and see if the problem comes back. I'll try to remember to post the results of that experiment.

Have you changed your database drivers? I noticed that there doesn't seem to be a very thorough testing of the database drivers in use by the non-windows ColdFusion installs.

It seems that almost every contract job I go to where they are using ColdFusion on something other than Windows, we have had to play 'musical chairs' with the drivers in a attempt to find one that works well with a particular configuration of the operating system, Java, ColdFusion and the database connection.

At one of my more recent jobs, Adobe has been working with the client for months in an attempt to find a driver that will work well for that flavor of Solaris and Oracle.

We used FusionReactor to help us narrow down that the data connection was dieing between ColdFusion and the Oracle database and that the 'death' of the connection would end up casuing ColdFusion to lock up.

I hope you have better luck than I did at that client. It's been four months now and quite the number of different Oracle drivers. I just heard this morning that they are going to give the Oracle thin client driver another go.