Port3101.org : Your BES Connection

Port3101.org : Your BES Connection (http://www.port3101.org/index.php)
-   Port 3101: The BES Admin Bar & Grill (http://www.port3101.org/forumdisplay.php?f=2)
-   -   blackberry dispatcher events (http://www.port3101.org/showthread.php?t=451)

nickadelman 02-02-2009 02:15 PM

blackberry dispatcher events
 
I'm getting the following events in the event log in the order shown. They can vary in time between a few seconds or a half hour. I have a bunch of questions:
Why SRPClient trying to connect to localhost?
Is this a bug? Is there a fix?
Are there any troubleshooting tools I can use to diagnose the problem?

Event Type: Warning
Event Source: BlackBerry Dispatcher [SERVERNAME]
Event Category: None
Event ID: 20000
Date: 2/2/2009
Time: 10:38:26 AM
User: N/A
Computer: [SERVERNAME]
Description:
SRPClient::Connect: Error calling host "localhost" [127.0.0.1] (0)

Event Type: Warning
Event Source: BlackBerry Dispatcher [SERVERNAME]
Event Category: None
Event ID: 20460
Date: 2/2/2009
Time: 10:38:26 AM
User: N/A
Computer: [SERVERNAME]
Description:
[SRP] Connection failed

Event Type: Information
Event Source: BlackBerry Dispatcher [SERVERNAME]
Event Category: None
Event ID: 50096
Date: 2/2/2009
Time: 10:38:58 AM
User: N/A
Computer: [SERVERNAME]
Description:
[SRP] Dispatcher\SRP Connection established

Cheese Sammich 02-02-2009 02:18 PM

Sounds to me like your Internet connection is bouncing.

Otto 02-02-2009 02:25 PM

If I'm not mistaken, the Dispatcher service connects to the Router service which connects to the SRP infrastructure over the WAN. I believe this would be the reason you'll see the loopback designation for the initial connection (127.0.0.1/localhost), as Dispatcher->Router would be local on that server (over a certain port). I would think that if your Router was on another server or in the DMZ, then you may see something different in the designation.

nickadelman 02-02-2009 02:29 PM

that's what i thought but none of our other servers, routers or firewalls are showing anything happening at the times of the outage. i've als checked to make sure there are no firewall rules on the server and on the firewall preventing traffic on port 3101.

what concerns me is that the SRPclient is looking for something locally (thus the localhost and loopback address). that doesn't make sense, since (and i quote) ahem...
Quote:

"Server Routing Protocol (SRP) is the proprietary network protocol used to transfer data between a BlackBerry Enterprise Server and the Research In Motion BlackBerry infrastructure.

SRP communication takes place on TCP port 3101 by default."

http://en.wikipedia.org/wiki/Server_Routing_Protocol

so why would it be trying to loopback for something?

color me mindboggled....

Otto 02-02-2009 02:30 PM

See my response. Only the BlackBerry Router should make a connection outside of that server. All other traffic is locally routed on the server to its various components.

nickadelman 02-02-2009 02:32 PM

Quote:

Originally Posted by Otto (Post 3621)
If I'm not mistaken, the Dispatcher service connects to the Router service which connects to the SRP infrastructure over the WAN. I believe this would be the reason you'll see the loopback designation for the initial connection (127.0.0.1/localhost), as Dispatcher->Router would be local on that server (over a certain port). I would think that if your Router was on another server or in the DMZ, then you may see something different in the designation.

ok that makes sense... but then why would it be getting dropped? since if it's loopback (and if i'm not mistaken), the traffic never leaves the network card. so i guess it's gotta be something on that server, huh?

Otto 02-02-2009 03:22 PM

I see these in my environment as well. From the DISP log, I see the following entries:

[30000] (01/28 17:35:54.370):{0x1448} SRPClient::ReceivePacket: No received bytes (0)
[30000] (01/28 17:35:54.370):{0x8D4} [DIAG] EVENT=Unregister_thread, THREADID=0x8D4, THREADNAME="SRPClientReceiver"
[30000] (01/28 17:35:54.370):{0x2254} [SRP] Connection lost
[30000] (01/28 17:35:54.573):{0x2254} [SRP] Connection established
[50096] (01/28 17:35:54.573):{0x2254} [SRP] Dispatcher\SRP Connection established
[30000] (01/28 17:35:54.573):{0x2120} [DIAG] EVENT=Register_thread, THREADID=0x2120, THREADNAME="SRPClientReceiver"

With that said, it's reported to the Event Log as an Informational notice only, so I don't think RIM considers it an issue. It appears to be more of a recycling of a thread than any actual drop.

I typically have Informational alerts disabled from logging in the Event Log, so I would have never noticed these anyhow (but it appears that I may have not disabled the logging on my test server).

nickadelman 02-02-2009 03:44 PM

cool... so not much to worry about, even if they are frequent... pretty much just a BES system burp

on a side note, i see that you guys are certified... worth it?

jsplit 02-02-2009 05:06 PM

Quote:

Originally Posted by nickadelman (Post 3644)
cool... so not much to worry about, even if they are frequent... pretty much just a BES system burp

on a side note, i see that you guys are certified... worth it?

exactly - just a hiccup.

Otto 02-03-2009 12:27 AM

Quote:

Originally Posted by nickadelman (Post 3644)
cool... so not much to worry about, even if they are frequent... pretty much just a BES system burp

on a side note, i see that you guys are certified... worth it?

Since I passed both during the beta periods, I thought it was pretty cool to be one of the first ever to do it, but I simply got a pat on the back and recognition MONTHS after I received acknowledgement of a passing grade. No raise, which wasn't necessarily expected. I got the BCX-410 for free and paid half price for the BCX-610 out of pocket (as to not be tied down by any obligation to the company, should that ever come up). Since it's a new certification, I think it would only hold some weight within this particular niche of the industry. I'll be getting my MCITP:EMA or MCITP:ESA at some point this year. That should land me a promotion and a raise (I hope so, at least).


All times are GMT -4. The time now is 11:12 AM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


SEO by vBSEO 3.3.2 PL2