Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Server fatal fail with exit code 132 and no log #24

Open
michalhosna opened this issue Apr 5, 2019 · 0 comments
Open

Server fatal fail with exit code 132 and no log #24

michalhosna opened this issue Apr 5, 2019 · 0 comments
Assignees
@rafiki270
Labels
bug Something isn't working

Comments

@michalhosna
Copy link
Contributor

Server fails without any message on stdout/stderr and exit code 132. It's probably some fatal error.

Some examples:

  • Env variable APICORE_SERVER_PATH_PREFIX set to "'', then any request on a valid endpoint, will crash the server.
  • Env variable APICORE_SERVER_URL set to http://0.0.0.0:8080 hen any request on a valid endpoint, will crash the server.
@michalhosna michalhosna added the bug Something isn't working label Apr 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rafiki270 rafiki270

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rafiki270 @michalhosna