--serve :myport doesn't listen to myport #70
Description
I'd expect this to listen to the port 12345 with the intent the remote hosts being able to connect. But using ss -tulpn, I don't see any process listening on 12345: PERFORATOR_ENDPOINT=my_hostname ~/workspace/repos/perforator/perforator/cmd/cli/perforator record --serve 0.0.0.0:12345 -- sleep 60. Same result with --serve :12345.
Perforator was built on the host directly (Ubuntu 24.04.3 LTS) following https://perforator.tech/docs/en/guides/build#host and using the command ./ya make -r perforator/bundle.
Perforator's output:
13:50:57.892 INFO profiler.BPF machine/bpf.go:172 Successfully initialized eBPF program
13:50:57.892 INFO profiler.perfevent perfevent/bundle.go:152 Parsing CPU list
13:50:57.892 INFO profiler.perfevent perfevent/bundle.go:157 Parsed CPU list {"cpu_count": 32}
13:50:57.902 INFO profiler profiler/profiler.go:558 Trying to enable AMD BRS perf-event
13:50:57.906 INFO profiler.ProcessRegistry upload/uploader.go:102 New upload scheduler {"config": {"MaxClosedBinariesQueue":1000000,"MaxSimultaneousUploads":30,"UploadedBinaryCacheConfig":{"ExpirationMaxJitter":1200000000000,"ItemTimeout":600000000000,"MaxSize":10000}}}
13:50:57.911 INFO profiler profiler/profiler.go:418 Loading kallsyms
13:50:58.054 INFO profiler profiler/profiler.go:423 Successfully loaded kallsyms {"num_symbols": 207429}
13:50:58.054 INFO profiler profiler/profiler.go:426 Loading cgroupsfs state
13:50:58.054 INFO profiler profiler/profiler.go:431 Loaded cgroupfs state {"cgroupfs_version": "V2"}
13:50:58.054 INFO profiler profiler/profiler.go:444 Preparing profiler config
13:50:58.054 INFO profiler profiler/profiler.go:674 Selected cgroup engine {"engine": "CgroupEngineV2"}
13:50:58.054 INFO profiler profiler/profiler.go:706 Configuring the profiler {"config": {"TraceKthreads":false,"TraceWholeSystem":false,"EnableJvm":false,"EnablePhp":false,"ActiveCgroupEngine":2,"PidFilter":0,"PidnsInode":4026531836,"SchedSampleModulo":100,"SignalMask":0}}
13:50:58.054 INFO profiler profiler/profiler.go:243 Successfully initialized profiler
13:50:58.054 INFO profiler profiler/profiler.go:1105 Registered process {"pid": 1136650}
13:50:58.055 INFO profiler.perfmap perfmap/registry.go:368 Perf map refresh finished {"tracked_processes": 0, "refreshed_processes": 0, "refresh_errors": 0, "total_current_symbols": 0, "total_rebuild_time": "0s"}
13:51:08.071 INFO profiler profiler/profiler.go:1003 Saved profile {"labels": {"host":"my_hostname","kernel":"6.8.0-83-generic","pid":"1136650"}, "samples": 38}
13:51:13.056 INFO profiler.perfmap perfmap/registry.go:368 Perf map refresh finished {"tracked_processes": 0, "refreshed_processes": 0, "refresh_errors": 0, "total_current_symbols": 0, "total_rebuild_time": "0s"}
13:51:18.099 INFO profiler profiler/profiler.go:1003 Saved profile {"labels": {"host":"my_hostname","kernel":"6.8.0-83-generic","pid":"1136650"}, "samples": 177}
13:51:18.600 ERROR profiler.perfmap perfmap/registry.go:96 Process already registered {"pid": 1136607}
13:51:23.165 ERROR profiler.perfmap perfmap/registry.go:96 Process already registered {"pid": 503627}
13:51:23.863 ERROR profiler.perfmap perfmap/registry.go:96 Process already registered {"pid": 503627}
13:51:28.056 INFO profiler.perfmap perfmap/registry.go:368 Perf map refresh finished {"tracked_processes": 0, "refreshed_processes": 0, "refresh_errors": 0, "total_current_symbols": 0, "total_rebuild_time": "0s"}