You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a really odd one. If I'm reading this error right, upon starting up, baron tries to reach its own URL (via a proxy), and throws and exception and errors out if it can't.
However, it hasn't actually started up yet, so of course it's never going to be able to hit its own URL.
bitcoin@testlab:/home/src/baron$ node server.js | ./node_modules/.bin/bunyan -o long
[2015-11-23T03:16:27.782Z] INFO: test store/14920 on testlab: Baron Init: CouchDB is ready.
[2015-11-23T03:16:28.139Z] ERROR: test store/14920 on testlab: instantiateDb error
Error: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<title>503 Service Unavailable</title>
</head><body>
<h1>Service Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
<hr>
<address>Apache/2.4.7 (Ubuntu) Server at localhost Port 80</address>
</body></html>
at Object.createErr [as create] (/home/src/baron/node_modules/nano/node_modules/errs/lib/errs.js:97:11)
at Request._callback (/home/src/baron/node_modules/nano/nano.js:319:39)
at Request.self.callback (/home/src/baron/node_modules/nano/node_modules/request/request.js:236:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (/home/src/baron/node_modules/nano/node_modules/request/request.js:1142:14)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage.<anonymous> (/home/src/baron/node_modules/nano/node_modules/request/request.js:1096:12)
at emitNone (events.js:72:20)
The proxy server is working perfectly well (on both HTTP and HTTPS), but obviously this url will fail, because node isn't running.
Very confusing. I also don't understand why that's an instantiateDB error, it seems to connect to couch just fine.
The text was updated successfully, but these errors were encountered:
This is a really odd one. If I'm reading this error right, upon starting up, baron tries to reach its own URL (via a proxy), and throws and exception and errors out if it can't.
However, it hasn't actually started up yet, so of course it's never going to be able to hit its own URL.
The proxy server is working perfectly well (on both HTTP and HTTPS), but obviously this url will fail, because node isn't running.
Very confusing. I also don't understand why that's an instantiateDB error, it seems to connect to couch just fine.
The text was updated successfully, but these errors were encountered: