Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Better error message for port conflict #132

Closed
dmcassel opened this issue Sep 9, 2013 · 1 comment
Closed

Better error message for port conflict #132

dmcassel opened this issue Sep 9, 2013 · 1 comment

Comments

@dmcassel
Copy link
Collaborator

dmcassel commented Sep 9, 2013

If you bootstrap with a port that is already in use, Roxy vomits a bunch of hard-to-read error text. Detect the error and produce an easier-to-read message.

@peterskim12
Copy link
Contributor

Change error reporting to simply print out value of error:format-string/ to stdout and refers user to MarkLogic error log:

Bootstrapping your project into MarkLogic on localhost...
ERROR: ADMIN-PORTINUSE: (err:FOER0000) Port is currently in use
See MarkLogic Server error log for more details.
ERROR: ... Bootstrap FAILED

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants