system
November 5, 2013, 1:07pm
1
system
November 6, 2013, 11:17am
2
(imported comment written by Raja9109)
I/m also facing similar issue in LInux Relay after installing 9.0.649
system
November 7, 2013, 5:24am
3
(imported comment written by ToshikiMatsui)
Have you restarted both processes in its machine?
system
November 7, 2013, 10:24am
4
(imported comment written by Raja9109)
Yes . Already tried all the Possibilities
system
November 7, 2013, 4:58pm
5
(imported comment written by martinc)
What happens when you ping you loopback (127.0.0.1)?
When I look at my relays and the client logs, most show the 127.0.0.1 and they are working. I wonder if there is a firewall issue somehow blocking the loopback.
system
November 7, 2013, 5:24pm
6
(imported comment written by Raja9109)
I’m able to ping using loopack address and firewall is in disabled state. The issue is only with 9.0.649 early it was working fine with 8.2.1372
system
November 7, 2013, 5:33pm
7
(imported comment written by martinc)
Not sure if this is it or not:
http://www-01.ibm.com/support/docview.wss?uid=swg1IV45378
There were some relay fixes addressed in 9.0.777+
Relay
* Fixed issue where Relay is unresponsive during RegistrationList upgrade (issue #58548, APAR: IV45378)
* Fixed issue where Relay posts incorrect Content-Type causing report send/receive failure (issue #58808
I do not have an 8.2 build that I can try to upgrade and see what happens. I am currently on 9.0.787 and my relays seem to be functioning correctly.
system
November 7, 2013, 6:17pm
8
(imported comment written by Raja9109)
Thanks for your valuable suggestion. This issue is happening only on few Relays . I logged a PMR with IBM and awaiting for response from them.
system
November 7, 2013, 6:32pm
9
(imported comment written by martinc)
No prob. I was going to suggest the PMR route
Couple things they will probably ask (if not already)
Turn on the debug logging for the agent. (BES Client Setting: Enable Debug Logging).
Consider an upgrade (sorry LOL).
I wonder if you can set the agent to manual and set the relay to a different relay. Just to see if it will complete the registration.
system
November 8, 2013, 12:54pm
10
(imported comment written by RadekChan)
The other clients which connect to the relay are working. The problem is just the client connect to its relay.
So, wonder if we can set it not to connect 127.0.0.1, and using other IP/FQDN.
system
November 8, 2013, 4:14pm
11
(imported comment written by Raja9109)
Hello Martin,
I have not received any update from IBM yet. After relay installed , the client default behavior is connect through locally (127.0.01) i dont think so we can change this.
system
November 8, 2013, 6:48pm
12
(imported comment written by martinc)
Can you try the command:
telnet 127.0.0.1 52311
and then try
telnet 10.128.177.15 52311
I am sure that the second one should connect, but the first one should fail. If that is failing, we have some other networking issue on that system. I think this is where to start. Find out why it is not listening to port 52311 on the loopback.
All the remote systems would be using either the FQDN or the ip of the relay to connect. It is only when the agent is on the same system as the relay that it uses the loopback, so this is something unique to a relay system.
Do you have the system set to automatic or manual relay config? If it is manual, then you could try automatic, but I think you would have to manually set up the registry keys since you probably cannot execute actions on it
system
November 11, 2013, 8:24am
13
(imported comment written by RadekChan)
The localhost telnet is working. So it seems like the software problem.
I updated the client and relay to 9.0.787.0, but still the same.
Trying 127.0.0.1…
Connected to 127.0.0.1.
Escape character is ‘^]’.
The client seems like listening, but not accept register.
curlhttp://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=Version
ClientRegister
Version 9.0.787.0
curlhttp://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe
curl: (52) Empty reply from server
system
November 11, 2013, 3:58pm
14
(imported comment written by Raja9109)
Whatever Mr.Chan said, The same things happening in my Linux Relay box as well.
system
November 11, 2013, 7:13pm
15
(imported comment written by RadekChan)
This time I tried to downgrade to 9…0.586 and still the same.
I am thinking would it be OS version problem.
The Relay/Client rpm is for RHEL 5 and my server is RHEL 6.
system
November 12, 2013, 7:06pm
16
(imported comment written by RadekChan)
Well… I downgraded the client and relay back to 8.2.1409.0. And it looks like working fine…
So I think it should be a bug in version 9 ?
One more information is my problem “relay” server is connecting to a “top relay” server. Would it be the point that problem happened?
Raja9109 , are you the same?
system
November 13, 2013, 10:49am
17
(imported comment written by RadekChan)
I found the problem in debug log.
I am testing version 9.0.787 now.
When I start the relay, the client is able to connect to my top relay due to besrelay.conf
And after awhile, the client register again.
This time the client direct register to IEM server instead of my top relay. Since the client do not have network connection to the IEM server. So it cannot be registered.
So the point is why the client will register to IEM server, but not top relay after the first register.
I stated top relay in besrelay.conf
[Software\BigFix\EnterpriseClient\Settings\Client_Enterprise Server_ClientRegister_ParentRelayURL]
Relay Selection: Attempting to register via local relay to potential parent.
system
November 13, 2013, 3:26pm
18
(imported comment written by Raja9109)
The same thing happened in my linux relay box as well.
system
November 18, 2013, 9:49am
19
(imported comment written by Raja9109)
Hi Radek,
did you find the root cause? I’m not getting proper response on PMR which i raised for this issue.
system
November 18, 2013, 9:57am
20
(imported comment written by RadekChan)
No…
Only can identify the problem is the client “Attempting to register via local relay to potential parent” to IEM server instead of my top level relay.
But not yet found the solution.
