Primary Relay Issues

Usage and Config Platform
1

(imported topic written by mholder91)

My primary relay ran out of disk space last night and now I can’t get any of the clients to respond. I’ve corrected the disk space issue, rebooted both the root server and the primary relay, but since everything is routed through the primary relay, including all other relays, nothing is responding anymore. Many of the clients have up to date “last report times”, but none of them are responding to any actions. Actually, I take that back. I deployed a service pack task to a handful of machines last night and targeted them by a manual group. All of the machines in this group are now showing as having the SP installed, but the task that I deployed isn’t even registering any applicable machines. The deployment health check dashboard shows that all of my relays are several actionsite versions behind. As a matter of fact, they’re all stuck on the exact same version.

Does anyone have any suggestions?

Should I just open a support case?

What would be the repurcussions if I uninstalled and re-installed the primary relay?

Any help is appreciated. Thanks.

2

(imported comment written by MattBoyd)

The relay that you’re referring to is a top level relay and NOT the BES server itself, correct? Uninstalling and reinstalling your primary (top level) relay will probably fix the problem. I’d expect the relay to be very busy after it’s reinstalled, but it should level out after a while.

Be sure to verify your relay settings after reinstalling. You may have to set them again.

3

(imported comment written by mholder91)

Yes, it is the top level relay – NOT the BES root server. I ended up uninstalling the relay and reinstalling it. Things do seem to be responding now, but you are right – it seems to be quite busy while everything “catches up”. Also, it’s taking quite a while for the secondary relays to start reporting back to the newly installed top level relay, but they are eventually responding. Thanks for your help.