18NoSiteIDMatchesURL error

I’m trying to create a copy of my production root server for upgrade testing and had it going for a bit (I thought), but hit a snag. In the BESRelay.log I’m getting:

u, 06 Sep 2018 13:08:51 -0400 - /masthead/masthead.afxm (2250229504) - Unable to find site id for URL: http://bes.domain.com:52311/cgi-bin/bfgather.exe/actionsite
Thu, 06 Sep 2018 13:08:51 -0400 - /masthead/masthead.afxm (2250229504) - MastheadPlugin Error: 18NoSiteIDMatchesURL

Getting my Google on didn’t show much promise. Any idea what I need to do next to troubleshoot?

Because I hate leaving things incomplete. it was a combination of cleaning up 2 things documented here:

https://www-01.ibm.com/support/docview.wss?uid=swg21994391
and
https://www-01.ibm.com/support/docview.wss?uid=swg21697473

After services were brought back up, I had to wait a while. The same error message was showing up in the RD page for a bit, but it cleared up as things rebuilt.

I have a very similar error with 9.5.14. The 2 links of the solution aren’t available anymore. Could you please describe what needed to be cleaned to fix the issue?

The message is not because a specific version of Bigfix, it is not an error and in general is not something to worry about.

It point out just that one or more agents are requesting for a site ( external, operator or custom ) no more existing on the server, probably because have been deleted.

If the message is visible on the log file of a relay and it is really desired remove them, the two old tech notes in previous comments just suggest a gather reset of that relay and are equivalent to the following KB:
https://hclpnpsupport.hcltech.com/kb_view.do?sysparm_article=KB0023512

If the message is visible in the server log file instead, the gather reset procedure to be performed is the following ( do not use the procedure for the relay, would leave the server in a inconsistent status ):
https://hclpnpsupport.hcltech.com/kb_view.do?sysparm_article=KB0023994
but in this second case, even if the procedure can be safely attempted, it is not said it alone would fix the message, so could be necessary open a case and involve the support team.

Hi, I also have the same issue, but am unable to open any of the four links above.
I particularly interested in the procedure for the server please.
Would it be possible to paste the details in a response please?
Cheers.

Unless you’re having a huge number of them, you can safely ignore the message. It’s a considerable effort to cleanup with not much benefit in many cases.

I think what you’re looking for is a “Gather State Reset”. Start with the lowest-level relays and work your way up.

Relay procedure at https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0079078

Root server procedure at https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0023994

1 Like

perfect… Many thanks Jason :slight_smile:

1 Like