Open hakansa opened 3 years ago
@hakansa It seems compilation is stuck or something so server is not started hence you can't ping.
export GOFLAGS=-x
and then run make run-server
and we can try to figure out why compilation is stuck.
@streamer45 @agnivade Can you help take a look?
I guess I figured out that what happened;
When I run make run-server
again, the go run ./cmd/mattermost/main.go
process started but port 8065 is not listening. This time, I decided to wait. A few minutes later, mattermost-server process started to listening port 8065.
I think, there should be some signs so people understand they should wait.
I have some suggestions;
Instead of using go run ./cmd/mattermost/main.go
we can compile code first with go build ./cmd/mattermost/main.go -o ./bin/mattermost-server
and run the compiled binary if compilation success. I think that is important, because when I run make run-server
I couldn't understand why I'm waiting for. Binary to be compiled, or the server to be initialized?
There is no log message is printed until HTTP server started. If some log messages is printed during early initializations, people could figure out they should wait to finish initializations
@hakansa Thanks for the thorough feedback, it's highly appreciated. I agree that the user shouldn't be left guessing for (possibly) several minutes. I've created a ticket (MM-35029) to keep track of this.
@streamer45 thanks for the reply. Is it OK to change this issue's title to [MM-35029]Improve logging during make run-server
?
I'm currently working on another issue, when I finish to work on int maybe I can deal with this issue.
Sure, that would be great :+1:
Summary
I couldn't run mattermost-server on Ubuntu 18.04. I followed the Developer Setup
Steps to reproduce
Detailed information is below;
Expected behavior
Run mattermost server.
Observed behavior (that appears unintentional)
When I run
make run-server
, I got the following output;Everyting is OK so far, When I ping the server, I got the following error;
Port 8065 is not listening;
I think the mattermost-server process is running;
Possible fixes
-