Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 5082 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

So, we have a number of users using our FM Server. About half are on FMP clients, and the other half are only using IWP. Occasionally, we get a call from one of the IWP users saying that either web pages aren't loading, or they get a message saying Service Unavailable. When I look at the processes running on our server (Apple Xserve 10.5.8), it's easy to spot the FM Web Publishing proccess because it is using 100% (or sometimes more, somehow!) of the CPU. Once we stop and restart the service, it runs fine again for anywhere from a few hours to a week.

The CPU usage kinda tells me that there is some hidden infinite loop in my code, and I'll keep looking for it, but I've also been reading the server logs, and found this interesting bit of information (some of it is edited because I'm not sure what I should and shouldn't post in terms of security):


2010-12-22 09:16:42 Server Events     Warning      Client "User (Computer Name)" [192.168.1.133] authentication failed on database "someDB.fp7" using "User[fmapp]".

2010-12-22 09:20:19 Publishing Engine Error        127.0.0.1:xxxxx - - "/fmi/conf/config.wpc" 401 0

2010-12-22 09:20:20 Publishing Engine Information  FM Web Publishing - - wpc1 Filemaker Server Web Publishing Engine Stopped

2010-12-22 09:20:20 Publishing Engine Information  ServerGroup "/fmi/conf/config.wpc" 200 2246

2010-12-22 09:20:23 Web Server        Error        [75955:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc1) Connecting to tomcat failed.  Tomcat is probably not started or is listening on the wrong port.

A few things to note:

1) The attempted login that failed was on a FMP Client, not an IWP User.

2) The Error 401 (Unauthorized) occurs almost 4 minutes after the FMP user fails to log in. Perhaps they're unrelated?

3) The publishing engine was not shut down by a user. The record here is it "crashing" or shutting down on it's own.

4) "ServerGroup" is an Admin group set up on the Xserver's Workgroup manager. Almost all authentication for our database is done via External Server.

Anyone have any thoughts as to whether this is explaining why the web server is crashing. Also, can someone either explain what some of these numbers mean (i.e. the 200 2246) or point me to a service that I can teach myself from?

Thanks a bunch.

This topic is 5082 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.