Closed ZaphodB closed 9 years ago
I have the exact same issue on FreeBSD 10.1
Zaphod, which OS are you on? When it happens, could you strace the whole thing? I can't reproduce here is the problem. Also, are you doubly sure you are connecting to [::]:8000 and not 127.0.0.1:8000?
RvdE: the strace question is for you as well of course ;-)
Ok, I can reproduce now. Pls wait.
Fixed in a33d01fa8f816cc760414861780291d326c7cf2a - this had to do with forking after creating threads, which appears to work differently on some architectures than others.
actually fixed one commit later, sorry
metronome does not seem to be responding to or even receiving packets on port [::]:8000 when daemonized.
When started via
$ ./metronome --daemon=0 --stats-directory=./stats Launched Carbon functionality on [::]:2003 Launched webserver on [::]:8000
it works as advertised.