Server Web is not reliable and safe.

[CROMERO@CONGRESOJAL]

:o

Hello, my name is Carlos Romero and I am a software engineer working in the
Congress of Jalisco, M?xico.


The reason why I contact you is because we have a problem using Cold Fusion Mx
7 and our server web.

We have a Server Web HP, PROLIANT ML 350 GENERATION 3.
CPU 3.6 GHZ, 1.00 GB of RAM,
Operative System: WINDOWS 2003 Server Service Pack 1
Microsoft IIS and SQL Server 2005

Four months ago, we installed Cold Fusion Mx 7. Sometimes, we can?t access to
our Web Site, but at the same time, it does respond to a PING.
At the end, in order to make our Web Site work again, we have to reboot the
Server.

We have some databases in Microsoft Access 2003 that we want to migrate to SQL
Server, but we can?t do it until we solve this problem, I mean that the Server
is not reliable and safe.

Do you have any idea of what is happening? Or do you know how to solve this?
I would really appreciate your help!

Looking forward to hearing from you
Sincerely
Carlos Romero.
Government of Jalisco

[ke4pym]

You're kind of in a catch-22. You really should dump Access as fast as you
can. That's going to go a *LONG* way towards getting your server stable.

Access should never, EVER be used for production systems.

It would be helpful if you could post some of your logs (server, application,
exception, etc) from just after the server crashed.

When the server crashes do you just reboot the whole thing? Or do you try to
restart just ColdFusion?

[LinuxInductee]

First: Agree with the Access thing, not a good solution, great
prototyper or data converter, but not a shared, database. I'd be
surprised if data corruption was not already a problem.

Second: Ping is a high priority, low overhead service. Your web server
could be functioning, albeit slowly.

Third: Dump IIS fast. Use Apache, even on Windows. I will need a book
to describe all the reasons why.

Fourth, consider clustering to maximize availability.

And lastly, ke4pym is right. Trace down what is causing the problem.
You could be getting attacked, DoS, or you could have some bad code, or
your firewall could have timing rules to stop traffic on port 80, or a
scan or defrag utility might be consuming resources, or any of many
other things. Start looking at the event log, IIS log, firewall log,
which, ahem, should be done in a public environment anyway. Without
someone reviewing the logs, you WILL have people hacking their way into
your system...especially using IIS on Windows....on that I will bet
your annual salary.