Rudder

Currently the agent will only output

@R: *************************************************************************

• rudder-agent could not get an updated configuration from the policy server. *
• This can be caused by a network issue, an unavailable server, or if this *
• node has not yet been accepted in the Rudder root server.
  **************************************************************************@

If we think of the folders refused / allowed on the server side if a client isn't accepted yet, those do differ.
So in truth a rudder client can indeed tell which of the following is true:

• I was not able to connect (refusal) - give error message about firewall and allowed subnets
• I was not able to download the initial promises update - give error message about (hm?)
• I was not able to fetch the folder named after my uuid - give error message that client isn't yet accepted in rudder or the acceptance hasn't propagated

I hope you get the idea. If i can i'll make a more detailed chart of cases.