Topic
  • 6 replies
  • Latest Post - ‏2014-10-27T22:47:37Z by SteveHull
ItsAvi
ItsAvi
11 Posts

Pinned topic 2 kinds of errors in v9 deployment

‏2013-07-01T07:49:16Z |

Hi,

i have 2 kinds of errors popping up on the top level relay in the DMZ, the one (and only) just below the TEM root,

1. is the error described in this KB:
http://www-01.ibm.com/support/docview.wss?uid=swg21506204

i would like to know if anyone know of a way to log the name of the client that asked for the sites that from an old deployment (this happens after we migrated to completely new license deployment, and apparently few client are connected but are asking for sites from old deployment)

2. every day i get a number of these, in logfile.txt of the top level relay in DMZ:

 Mon, 01 Jul 2013 08:51:44 +0200 - RelayNotifier5 (3568) - Error running task RelayNotifier5: HTTP Error 28: Timeout was reached: Connection timed out after 10000 milliseconds

Mon, 01 Jul 2013 08:51:57 +0200 - RelayNotifier5 (3568) - Error running task RelayNotifier5: HTTP Error 28: Timeout was reached: Connection timed out after 10000 milliseconds
Mon, 01 Jul 2013 08:52:09 +0200 - RelayNotifier5 (3568) - Error running task RelayNotifier5: HTTP Error 28: Timeout was reached: Connection timed out after 10015 milliseconds
Mon, 01 Jul 2013 08:52:34 +0200 - RelayNotifier5 (3568) - Error running task RelayNotifier5: HTTP Error 28: Timeout was reached: Connection timed out after 10015 milliseconds
Mon, 01 Jul 2013 08:52:57 +0200 - RelayNotifier5 (3568) - Error running task RelayNotifier5: HTTP Error 28: Timeout was reached: Connection timed out after 10000 milliseconds
Mon, 01 Jul 2013 08:53:34 +0200 - RelayNotifier5 (3568) - Error running task RelayNotifier5: HTTP Error 28: Timeout was reached: Connection timed out after 10000 milliseconds
 

what is a relaynotifier? i haven't seen it in my old deployment, i haven't seen it in my new deployment when we were running V8, enabling debug logging reveals no extra info on the nature of the requests.

apparently the 2nd issue has already been posted by more users,
https://www.ibm.com/developerworks/community/forums/html/topic?id=07a45b8f-e3f3-4a33-ac62-52107cba6af8&ps=25

still need assistance on the 1st issue.

assistance will be much appreciated, thanks!

  • MaherBA
    MaherBA
    6 Posts

    Re: 2 kinds of errors in v9 deployment

    ‏2013-09-17T12:54:54Z  

    Hi,

    Do you have an explication to RelayNotifier issue please??

  • ItsAvi
    ItsAvi
    11 Posts

    Re: 2 kinds of errors in v9 deployment

    ‏2013-09-17T13:12:29Z  
    • MaherBA
    • ‏2013-09-17T12:54:54Z

    Hi,

    Do you have an explication to RelayNotifier issue please??

    Hi MetalMan,

    Nope, and i haven't seen anything written about it in the newest patch for V9 that came out yesterday.

  • MaherBA
    MaherBA
    6 Posts

    Re: 2 kinds of errors in v9 deployment

    ‏2013-09-17T13:18:08Z  
    • ItsAvi
    • ‏2013-09-17T13:12:29Z

    Hi MetalMan,

    Nope, and i haven't seen anything written about it in the newest patch for V9 that came out yesterday.

    Hi ItsAvi,

    Thank you, i haven't seen anything about it in IBM Endpoint Manager forum too :(

  • ItsAvi
    ItsAvi
    11 Posts

    Re: 2 kinds of errors in v9 deployment

    ‏2014-03-06T16:16:30Z  

    still not seeing a solution or a hint to what's causing this.

  • MarlonRojas
    MarlonRojas
    21 Posts

    Re: 2 kinds of errors in v9 deployment

    ‏2014-10-23T19:42:49Z  
    • ItsAvi
    • ‏2014-03-06T16:16:30Z

    still not seeing a solution or a hint to what's causing this.

    Dear friend we get same 2 issue when upgrade to 9.1.1.117, can you resolve your problem?

  • SteveHull
    SteveHull
    13 Posts

    Re: 2 kinds of errors in v9 deployment

    ‏2014-10-27T22:47:37Z  

    Neither of these errors indicate a problem on their own.  You only need to be concerned if you are seeing some other issue (e.g. clients are not responding to actions).

    You can track down clients causing the first error by looking in the BESRelay.log which should include the IP address requesting the bad site.  You'll have to follow that down the chain and check the log on any child relays eventually leading to the problem client.

    The second error may be expected if you have lower level relays reporting to the DMZ relay that are configured for polling due to network restrictions.  It indicates that the relay is timeout while trying to notify its child relay(s) of a new site.