zui icon indicating copy to clipboard operation
zui copied to clipboard

Zui fails to launch zed on port 9867

Open SpindlesDev opened this issue 2 years ago • 1 comments

Before opening a new issue, please make sure you've reviewed the troubleshooting guide: https://zui.brimdata.io/docs/support/Troubleshooting

Describe the bug Trying to launch Zui or Brim resulted in Connection Error. I looked through troubleshooting page and had stumbled into the issue when looking at the logs where it reported the following error

{
	"level": "error",
	"ts": 1684836220.2359428,
	"logger": "httpd",
	"msg": "Listen error",
	"error": "listen tcp 127.0.0.1:9867: bind: An attempt was made to access a socket in a way forbidden by its access permissions.",
	"stacktrace": "github.com/brimdata/zed/pkg/httpd.(*Server).Start\n\t/home/runner/work/zed/zed/pkg/httpd/server.go:42\ngithub.com/brimdata/zed/cmd/zed/serve.(*Command).Run\n\t/home/runner/work/zed/zed/cmd/zed/serve/command.go:119\ngithub.com/brimdata/zed/pkg/charm.path.run\n\t/home/runner/work/zed/zed/pkg/charm/path.go:11\ngithub.com/brimdata/zed/pkg/charm.(*Spec).ExecRoot\n\t/home/runner/work/zed/zed/pkg/charm/charm.go:63\nmain.main\n\t/home/runner/work/zed/zed/cmd/zed/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.19.9/x64/src/runtime/proc.go:250"
}

After checking with TCPView to confirm nothing was running on that way I had attempted to manually launching zed with higher permission which failed, after which I had tested on another port which worked. I had attempted to change mainDefaults via pkg.lake.port in package.json in a few different locations to have it launch zed automatically but to no avail. I know this is most likely a single user case issue, but could possibly be prevented with random port solution mentioned in #2040 but if that isn't an option maybe a way to manually specify a port to use instead would be possible?

Edit: After figuring out another issue I was having it could possibly be from the Windows 10 22H2 update. Ran into another issue that came from the update with SSLKEYLOGFILE variable causing programs to have OPENSSL_Applink issue. Will attempt to see if it replicates in a VM on 22H2 or just an issue with current Windows install

To Reproduce Unknown as many things have changed on computer since I last used Zui...

Expected behavior Zed to be able to launch and communicate with Zui

Screenshots

Desktop Info

  • OS: Windows 10 Pro 22H2
  • OS Version: 10.0.19045 Build 19045
  • Zui Version: 1.1.0

SpindlesDev avatar May 23 '23 10:05 SpindlesDev

@SpindlesDev: Thanks for reporting and circling back with the additional theory about root cause. We've thought about this class of problem before and both the "random port" and "manually select a port" approaches have been considered. We'll look at adding at least one of those soon so users won't be as stuck when this kind of thing happens in the future.

philrz avatar May 25 '23 15:05 philrz