Closed bigBron closed 3 years ago
Hey @bigBron, nice to meet you. Could you please share your config and version of the RR?
@48d90782 Sorry, no more details. I have deleted the project. It should be the latest version. It is installed with composer. The configuration file is the default configuration. I looked at the source code, use -d option will be fixed listening port 6061, whether the program can be adjusted to be more flexible?
@bigBron That depends on the version you use. But in general, -d
flag in the RR2 is the debug/pprof flag which you should not use other than for profiling your own plugin or profiling RR2 itself.
For the application, you have http.address
or rpc.address
for the RPC.
Is it possible to configure the debug/pprof port instead? In some cases 6061 will be occupied? https://github.com/spiral/roadrunner-binary/blob/3eeefb48d27084bc63474da09735feb583344a3b/internal/cli/root.go#L71-L74
Not at the moment, but just don't use -d
flag. It is for internal usage.
It's not equivalent to the RR1 -d
flag which was used to show debug messages. Debug logging level can be configured by adding logs
section. See: https://github.com/spiral/roadrunner-binary/blob/master/.rr.yaml
Oh. dude, I confused the concept, thank you for your patience reply.
@bigBron np, I'll check the report you sent and if I confirm it we will definitely fix it 💯
@bigBron Sorry, I can't reproduce your error. It seems, that when you used -d
flag, some other application already listened to the :6061
port on some interface:
I'm closing this ticket, but, feel free to reopen it if you for some unknown reason still have this issue.
in windows system run rr.exe serve command with -d option that get error prompt: