If you're pointing moxi at the wrong server/URL, or moxi can't
reach any of its REST/URL's, you'll see output prefixed with the
shell> ./dev/moxi/moxi http://foo.bar.baz.foo ERROR: could not contact REST server(s): http://foo.bar.baz.foo ERROR: could not contact REST server(s): http://foo.bar.baz.foo
You can see that moxi retries its configured REST/URL's every second. Also, if the server that moxi is contacting is up, but provides mangled JSON information, moxi will also inform you every second.
shell> ./dev/moxi/moxi http://google.com 2010-11-01 16:14:43: (agent_config.c.453) ERROR: could not parse JSON from REST server: <HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8"> <TITLE>301 Moved</TITLE></HEAD><BODY> <H1>301 Moved</H1> The document has moved <A HREF="http://www.google.com/">here</A>. </BODY></HTML>
When you provide moxi with a list of REST/URL's, the earlier URL's have higher precedence. So, moxi will favor the first URL and attempt to contact it first. Then the 2nd URL, then the 3rd and so on. If the 2nd URL works, but stops working (moxi succeeded in contacting the 2nd URL, but loses its connection to the 2nd URL some time later), moxi will start over from the start of the REST/URL's list with the first URL (in the hopes that the favored earlier URL is now back online).
Please see: Chapter 7, Moxi Error Responses