orbstack: Exited abnormally with signal 9

Describe the bug

OrbStack exited abnormally with signal 9. So I’ve checked logs and found this:

📦 scon | INFO[05-30 05:51:05] add forward                                   spec="{:: 18083 tcp}"
📦 scon | WARN[05-30 05:51:05] failed to apply listener changes              notAdded="[{0.0.0.0 7000 tcp} {:: 7000 tcp}]" notRemoved="[]"
📦 scon | ERRO[05-30 05:51:05] failed to update listeners                    container=docker error="listen tcp4 0.0.0.0:7000: bind: address already in use\nlisten tcp 0.0.0.0:7000: bind: address already in use"

...

📦 scon | INFO[05-30 05:51:57] remove forward                                spec="{0.0.0.0 7001 tcp}"
📦 scon | INFO[05-30 05:51:57] remove forward                                spec="{0.0.0.0 7000 tcp}"
📦 scon | INFO[05-30 05:51:57] remove forward                                spec="{:: 7001 tcp}"
📦 scon | INFO[05-30 05:51:57] remove forward                                spec="{:: 7000 tcp}"
📦 scon | WARN[05-30 05:51:57] failed to apply listener changes              notAdded="[]" notRemoved="[{0.0.0.0 7000 tcp} {:: 7000 tcp}]"
📦 scon | ERRO[05-30 05:51:57] failed to update listeners                    container=docker error="forward does not exist\nforward does not exist"

So the port number 7000 conflicts to other service that OrbStack exited with signal 9.

With this command, Can see the port number 7000 is already use in Control Center:

$ sudo lsof -PiTCP -sTCP:LISTEN 

OrbStack  2986 *****   72u  IPv6 0x*****     0t0  TCP *:4101 (LISTEN)
ControlCe 3368 *****    5u  IPv4 0x*****      0t0  TCP *:7000 (LISTEN)
ControlCe 3368 *****    6u  IPv6 0x*****      0t0  TCP *:7000 (LISTEN)
ControlCe 3368 *****    7u  IPv4 0x*****      0t0  TCP *:5000 (LISTEN)
ControlCe 3368 *****    8u  IPv6 0x*****      0t0  TCP *:5000 (LISTEN)

https://discussions.apple.com/thread/250472145?answerId=250901379022#250901379022

The port number 7000 and 5000 in MacOS is for AirPlay receiver. I think OrbStack should use another port instead of 5000 or 7000 but not sure.

To Reproduce

Steps to reproduce the behavior:

  1. Turn on OrbStack
  2. Turn On AirPlay receiver in System Settings
  3. Use docker container like mysql in local
  4. See error on OrbStack

Expected behavior

OrbStack exited abnormally with signal 9

Screenshot 2023-05-30 at 3 19 48 PM

Environment

  • OrbStack info:
    • Version: 0.11.0 (110000)
    • Commit: 26e09531a8770bcfbaacc3723b091639f0f6d0dd (v0.11.0)
  • System info:
    • macOS: 13.4 (22F66)
    • CPU: arm64, 10 cores
    • CPU model: Apple M1 Pro

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Comments: 18 (8 by maintainers)

Most upvoted comments

There was an edge case in older versions where the service could keep getting killed when running mismatched or duplicate GUI and service versions. It’s no longer possible to run multiple copies of the GUI app since v0.12.0, so this should no longer happen.

If you’re still experiencing this issue, let me know and I’ll reopen this issue.

@punkyoon Can you also check if the issue still occurs on OrbStack v0.11.2?

I’m still getting that error 😢

However, since I had previously installed OrbStack while using Rancher Desktop and had docker and docker-compose installed separately, I thought this might be the problem, so I uninstalled Rancher Desktop, docker, docker-compose, and OrbStack.

When I reinstalled OrbStack, I got the same error in the same situation, so I tried to use eslogger to see what was going on, but it didn’t happen again, so I guess I’ll have to wait and see.

Ok, let’s find out what’s killing OrbStack.

Start OrbStack (CLI or GUI, doesn’t matter) and run the following command on macOS ASAP:

sudo eslogger signal

Stop eslogger and share the output once the error occurs. It will be long and you may need to redirect it to a file.