PROBLEM: TREX Http Server Not Available

[Former Member]

I have just deployed SPS11 and everything seemed to be fine. However I appear to be having a problem with the Http Server as the status is set to red and the service is not available.

I have checked all of the post installation config. and all that is fine.

Is there anything else for me to check as I need to get it started?

Thanks

[Former Member · Accepted solution]

Hi Phil,

did you specify the address of the TREX Name Server?

Visual Admin, Click on Cluster and navigate to Services -> TREX Service. Enter the address of the TREX name server into the parameter nameserver.address.

tcpip://<host_name_of_trex_host>:<name_server_port>

In a cluster environment, you have to do this on each server node!

Is your TREX well started? Can you see these processes?:

Unix: httpd, TREXDaemon.x, TREXIndexServer.x, TREXNameServer.x, TREXPreprocessor.x, TREXQueueServer.x, TREXRfcServer.x

win:TREXDaemon.exe, TREXIndexServer.exe, TREXNameServer.exe, TREXPreprocessor.exe, TREXQueueServer.exe, TREXRfcServer.exe

What about the test scripts? Are they working fine?

Regards

Steffen

[former_member66232]

Can anyone post the solution to the above problem with the Localwatchdog error.

I am having a similar problem but with the Index server.

The trace error is:

[00556] 2005-11-14 16:12:12.101 e NameServer WatchDog.cpp(00060) : LocalWatchDog takes 60 seconds for 'indexserver@20qal7:30003'. Communication problem or interval (10 seconds) too short?

[00556] 2005-11-14 16:12:12.117 e TNS_Timing WatchDog.cpp(00073) : info LocalWatchDog: detected inactive indexserver@20qal7:30003

[00556] 2005-11-14 16:13:12.132 f NameServer TREXNameServer.cpp(00565) : pingTREXService(20qal7:30003) net exception, ping timeout: 60000 mls; ReadChannelException at BufferedIO.cpp:442

message: an error occured while reading from the channel

info: timeout occured

param: 172.16.10.207:30003

[00556] 2005-11-14 16:13:12.132 e NameServer WatchDog.cpp(00060) : LocalWatchDog takes 60 seconds for 'indexserver@20qal7:30003'. Communication problem or interval (10 seconds) too short?

[00556] 2005-11-14 16:13:12.132 e TNS_Timing WatchDog.cpp(00073) : info LocalWatchDog: detected inactive indexserver@20qal7:30003

The indexserver stops on a regular basis.

Appreciate any help.

Thanks

Paul.

[tombo_larsen]

Hi Phil

We have exactly the same error:

**********

e TNS_Timing WatchDog.cpp(00073) : info LocalWatchDog: detected inactive httpserver@http://<host>:38005/TREXHttpServer/TREXISAPIExt.dll

**********

Could you please describe what the solution was?

BR

Tom Bo

[Former Member]

Hello Tom,

maybe this thread from me could be helpful:

/thread/71527 [original link is broken]

Regards

Alex

[Former Member]

Hi Phil,

are you still facing your problem?

Sorry, but I was "away"...

S.

[Former Member]

All sorted now thanks!

[Former Member]

Hello Phil,

I have mybe the same problem. Looks like you have resolved it. Can you please let me know how?

Thanks and Regards

Alex

[Former Member]

I have a message in one of the Traces which is:

[01748] 2005-07-14 14:54:01.958 e TNS_Timing WatchDog.cpp(00073) : info LocalWatchDog: detected inactive httpserver@http://demosystem:30205/TREXHttpServer/TREXISAPIExt.dll

[Former Member]

Dear Phil,

Now I meet the same problem. If you have resoved it,would you post me?

[Former Member]

All,

Please look at note 1008299. It may help.

regards,

Paul

[Former Member]

Hello,

i got the same problem, but i was running an windows x64 platform.

so the solution i'll give there is concerning such a platform (64 bits) , so in this order :

1/ apply note : 1008299 - TREX 7.0: Configuring IIS on Windows 2003 64-Bit

2/ apply note : 1029783 - TREX 7.0 Httpserver does not work in 64 Bit Windows

3/ finally apply this last one : 917389 - TREX 7.0: TREX application pool in IIS not started

After restarting the application pool of TREX from IIS mangement console, you'll find that the trex httpserver is now running.

Lakhdar Mourad

[Former Member]

Thanks. Solved my problem on X64 windows server

[Former Member]

The config was fine before the upgrade to SP11 so I assume that us ok.

How would I know if the Python scripts were running?

[Former Member]

Make sure that the Web server has started and that the World Wide Web Publishing Service is running.

What about your configuration of your webserver?

Are the python test scripts running?

[Former Member]

Yeah the nameserver is tcpip://demoserver:30201 and seems to be ok.

All the .exe's are running. And TREX is running.

What do you mean by the test script? Also have updated the topology.ini file.

Still has not started!