Thanks Simon. Connection works fine, ping and curl run without a problem (got back the JSON with anonymous user)
On 5 December 2013 13:52, Simon Gaeremynck <gaeremyn...@gmail.com> wrote: > Hi Kabelo, > > That looks like a networking issue? > Can the second PP node resolve the globalAdminHost DNS name? > ping globalAdminHost > > If you’re running in EC2, can you reach > http://globalAdminHost:globalAdminPort ? You might need to tweak the > security group settings. > You can test it by doing a curl request like so: > curl -v http://globalAdminHost:globalAdminPort/api/me > Replace globalAdminHost and globalAdminPort by their respective config > values obviously. > It should respond with some JSON telling you’re an anonymous user on the > global admin server > > > Small tip: > It’s usually easiest if you point your PP to the nginx endpoint, that way > nginx will distribute the load generated by the PP across all app servers. > In that case the globalAdminPort should be 80. > > Simon > > > On 5 Dec 2013, at 08:26, Kabelo Letsoalo <kab...@opencollab.co.za> wrote: > > Thanks for the help. > > I have two PP nodes. My 2nd PP node is running on a different server (not > the same server as where my globalAdminHost is reachable by users). > > How do I configure the 2nd PP node? Pointing globalAdminHost to where the > admin UI is returns error: > > We could not log in on the tenant. The status of the content item will not > be set. (contentId=c:tenant:x1KwWPQxI) > err: { > "code": 500, > "msg": "Something went wrong trying to contact the server:\nread > ECONNRESET\nError: read ECONNRESET\n at errnoException (net.js:884:11)\n > at TCP.onread (net.js:539:19)" > } > > Thanks for the help. > > > On 4 December 2013 10:36, Simon Gaeremynck <gaeremyn...@gmail.com> wrote: > >> Hi Kabelo, >> >> That looks like the PP can't connect to an app server. >> >> Make sure you've configured the `config.servers` block appropriately >> (especially the globalAdminHost and globalAdminPort fields). >> Also ensure that the `credentials` block in the `config.previews` block >> is appropriately filled in. >> >> Kind regards, >> >> Simon >> >> On 4 Dec 2013, at 08:12, Kabelo Letsoalo <kab...@opencollab.co.za> wrote: >> >> > Got an unexpected error from the REST api. >> > Error: connect ECONNREFUSED >> > at errnoException (net.js:884:11) >> > at Object.afterConnect [as oncomplete] (net.js:875:19) >> > [2013-12-04T07:40:48.833Z] ERROR: oae-preview-processor/2336 on server: >> We could not get a signed token for the tenant. The status of the content >> item will not be set. (contentId=c:businesscollege:gkT_ovLJ8) >> > err: { >> > "code": 500, >> > "msg": "Something went wrong trying to contact the >> server:\nconnect ECONNREFUSED\nError: connect ECONNREFUSED\n at >> errnoException (net.js:884:11)\n at Object.afterConnect [as oncomplete] >> (net.js:875:19)" >> > } >> > >> > >> > On 4 December 2013 10:09, Kabelo Letsoalo <kab...@opencollab.co.za> >> wrote: >> > Hello. >> > >> > I'm getting an error from the preview processor reads: >> > >> > Got an unexpected error from the REST api. >> > err: { >> > "code": 401, >> > "msg": "Unauthorized" >> > } >> > >> > Seems to be a known issue. >> > >> > Appreciate the help! >> > >> > >> > See OpenCollab email disclaimer at >> http://www.opencollab.co.za/email-disclaimer_______________________________________________ >> > oae-dev mailing list >> > oae-dev@collab.sakaiproject.org >> > http://collab.sakaiproject.org/mailman/listinfo/oae-dev >> >> > > ------------------------------ > See OpenCollab email disclaimer at http://www.opencollab.co. > za/email-disclaimer > > > -- ------------------------------ See OpenCollab email disclaimer at http://www.opencollab.co.za/email-disclaimer
_______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
