Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Starting ASSETS_FRONTEND when the port's in use doesn't report an error #53

Open
rpowis opened this issue May 11, 2016 · 0 comments
Open

Comments

@rpowis
Copy link
Contributor

rpowis commented May 11, 2016

Steps to replicate...

$ cd $WORKSPACE/assets-frontend/
$ ./server.sh dev

Then in another shell...

$ sm --start AGENT -f # or any profile with a frontend

gives the output

'ASSETS_FRONTEND' version 'None' started with PID = 6335
Started: ASSETS_FRONTEND
All services passed healthcheck

but running sm -s doesn't list ASSETS_FRONTEND and the URLs 404.

The port conflict on 9032 doesn't get reported.

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

No branches or pull requests

1 participant