How are you subscribing the channels?

In the logs I see the URL specified as

http://blca-test. .com:5282/Marimba/InventoryService

How come there are whitespaces in the URL?

Please do a tuner admin to the workstation and check the value of marimba.security.trusted.transmitters property.

Sorry for that ! The subscription is failing majorly because of the transmitter not being accessible and network timeouts.

Is there any proxy connection set in the environment for accessing the BBCA transmitter?

[13/Apr/2012:10:27:43 +0300] - info SYSTEM 1052 Workspace flushed: Repeater list flushed for every channel because IP address changed.

This might be the cause of the issue. Check if the Endpoint'n subnet is changed. This might affect the access to the Repeater/Master Transmitter from the Endpoint.

I think that the repeater list would be flushed even when a system refreshes its IP within the same subnet.

Plus, they would have assigned all the possible IP Subnets for redirection to the repeater, in Implementation Phase if they are using SBRP.

Does the workstation have access to TCP/5282 on Master Transmitter and the local Repeater Transmitter and can the master transmitter and repeater access TCP/7717 on the workstation. If the answer is no, then you need to change the firewall settings.

Just do a quick test by enabling debug logs on any test workstation:

1. Stop the tuner service.

2. Enable debug logs by putting this property in prefs.txt file:

marimba.launch.javaArgs=-Xms64m -Xmx256m -DDEBUGFLAGS=TUNER=5

3. Start tuner service.

4. Open the Channel Manager.

5. Click Browse and browse to any channel and subscribe it.

6. Check the tuner history logs for any errors.

Adil's question regarding the proxy is an important one and I didn't see an answer to that -- please check the proxy settings on the client. Also, whilst a telnet from the client to 5282 on the Tx is useful, it would be even better if you can confirm that you can get a Tx listing using the affected client's web browser.

Looking at the error you are getting, it is a 608/818 error. This can have a number of root causes, but I have seen this if the clients timeout becuse a transmitter is taking a long time to respond.

Few questions:

1. Are you using repeaters?

2. In the repeater policy, is the master allowed to handle requests if no repeater responds?

3. Are all the repeaters up and running?

4. In the master (or mirror if you are using them) access log, do you see this incoming request and is it returning an error?

4. In the repeater access log, do you see this incoming request and is it returning an error?

regards,

Paul

From the history logs, it can be seen  that " A network error occurred: connection was timed out." May be the telnet is being interrupted because of the networl connection timeout...

Yes, the network connections are timing out. Now it needs to be confirmed whether it is a network bandwidth issue or an issue related to the availability of BBCA Infrastructure over the network.

It would be better to find answers to the questions pointed out by Paul i.e.,

1. Are you using repeaters?

2. In the repeater policy, is the master allowed to handle requests if no repeater responds?

3. Are all the repeaters up and running?

4. In the master (or mirror if you are using them) access log, do you see this incoming request and is it returning an error?

4. In the repeater access log, do you see this incoming request and is it returning an error?

and check if a proxy connectivity is required as well.

Hi

According to history log tuner doesn't retrive transmiter address.

major SYSTEM 1103 http://blca-test. .com:5282/Marimba/InventoryService: Error #600 occurred

Please give the proper IP address or hostname.domain name

try it