Homebrew / homebrew-core

🍻 Default formulae for the missing package manager for macOS (or Linux)
https://brew.sh
BSD 2-Clause "Simplified" License
13.74k stars 12.43k forks source link

MacOS Sequoia 15.1 use bind service occur reboot #196028

Open zouchengli opened 7 hours ago

zouchengli commented 7 hours ago

brew gist-logs <formula> link OR brew config AND brew doctor output

❯ brew info bind
==> bind: stable 9.20.3 (bottled), HEAD
Implementation of the DNS protocols
https://www.isc.org/bind/
Installed
/opt/homebrew/Cellar/bind/9.20.3 (316 files, 8.4MB) *
  Poured from bottle using the formulae.brew.sh API on 2024-10-29 at 16:45:12
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/b/bind.rb
License: MPL-2.0
==> Dependencies
Build: pkg-config ✔
Required: jemalloc ✔, json-c ✔, libidn2 ✔, libnghttp2 ✔, libuv ✔, openssl@3 ✔, readline ✔, userspace-rcu ✔
==> Options
--HEAD
    Install HEAD version
==> Caveats
To start bind now and restart at startup:
  sudo brew services start bind
Or, if you don't want/need a background service you can just run:
  /opt/homebrew/opt/bind/sbin/named -f -L /opt/homebrew/var/log/named/named.log
==> Analytics
install: 1,513 (30 days), 4,679 (90 days), 16,164 (365 days)
install-on-request: 1,420 (30 days), 4,377 (90 days), 14,784 (365 days)
build-error: 8 (30 days)

Verification

What were you trying to do (and why)?

I want use dns server test Because install bind service support my test

What happened (include all command output)?

Execute domain resolve command: ping github.com Occur Immediately reboot

image

What did you expect to happen?

image

Step-by-step reproduction instructions (by running brew commands)

brew install bind
sudo brew services start bind
sudo networksetup -setdnsservers Ethernet 127.0.0.1 
ping github.com
image
carlocab commented 7 hours ago

What is the output of brew config and brew doctor?

zouchengli commented 7 hours ago

What is the output of brew config and brew doctor?

image
carlocab commented 5 hours ago

Please don't use screenshots when sharing the output of commands in your terminal. They're often difficult to read and impossible to reuse (e.g. when looking up error messages). They also typically can't be parsed by screen readers. Instead, copy the text here and wrap them in three back-ticks (```) on the line before and on the line after to format them properly.

carlocab commented 5 hours ago

Does it behave the same way when you're not running in a VM?

zouchengli commented 4 hours ago

Does it behave the same way when you're not running in a VM?

same

zouchengli commented 4 hours ago

Please don't use screenshots when sharing the output of commands in your terminal. They're often difficult to read and impossible to reuse (e.g. when looking up error messages). They also typically can't be parsed by screen readers. Instead, copy the text here and wrap them in three back-ticks (```) on the line before and on the line after to format them properly.

chengli.zou@clz-vm-m1-max ~ % brew config
HOMEBREW_VERSION: 4.4.3
ORIGIN: https://github.com/Homebrew/brew
HEAD: 91f3671b16fe62121364c465c14e0dfd088d7ead
Last commit: 3 days ago
Core tap JSON: 30 Oct 01:44 UTC
Core cask tap JSON: 30 Oct 01:44 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 4
Homebrew Ruby: 3.3.5 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.5/bin/ruby
CPU: quad-core 64-bit dunno
Clang: 16.0.0 build 1600
Git: 2.39.5 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.1-arm64
CLT: 16.1.0.0.1.1729049160
Xcode: N/A
Rosetta 2: false
chengli.zou@clz-vm-m1-max ~ % brew doctor
Your system is ready to brew.
chengli.zou@clz-vm-m1-max ~ % 
ZhongRuoyu commented 1 hour ago

This problem doesn't seem specific to macOS 15.1. There are other reports from macOS 14.7 and 15.0:

zouchengli commented 1 hour ago

This problem doesn't seem specific to macOS 15.1. There are other reports from macOS 14.7 and 15.0:

It seems so, because I have been using this service for a long time, and it seems that this problem has appeared since the new system was launched this year. So has no one fixed this problem yet? I would like to ask whether this problem is a problem with the service itself or a problem with the system?

ZhongRuoyu commented 1 hour ago

It should be a kernel problem because a user space program should not cause a kernel panic like this.

I wasn't able to reproduce this on x86_64 macOS 15.1, so this may be specific to Apple Silicon. I encourage you to report this to Apple (via the "Problem Report for macOS" window in the screenshot you provided at the beginning), with the commands to reproduce this.

zouchengli commented 14 minutes ago

It should be a kernel problem because a user space program should not cause a kernel panic like this.

I wasn't able to reproduce this on x86_64 macOS 15.1, so this may be specific to Apple Silicon. I encourage you to report this to Apple (via the "Problem Report for macOS" window in the screenshot you provided at the beginning), with the commands to reproduce this.

image

OK,I have given feedback to Apple, but they may not reply or accept it.