8000 [bug] crc setup fail on windows as `crc daemon` hits panic to invalid pointer reference · Issue #4764 · crc-org/crc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[bug] crc setup fail on windows as crc daemon hits panic to invalid pointer reference #4764

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lilyLuLiu opened this issue May 20, 2025 · 2 comments · Fixed by #4765
Closed

[bug] crc setup fail on windows as crc daemon hits panic to invalid pointer reference #4764

lilyLuLiu opened this issue May 20, 2025 · 2 comments · Fixed by #4765
Assignees
@vyasgun

Comments

@lilyLuLiu
Copy link
Contributor
lilyLuLiu commented May 20, 2025 •
edited by anjannath
Loading

crc version: 05.20 main branch
bundle version: 4.18.2
platform: windows

PS C:\Users\crcqe> crc setup
CRC is constantly improving and we would like to know more about usage (more details at https://developers.redhat.com/article/tool-data-collection)
Your preference can be changed manually if desired using 'crc config set consent-telemetry <yes/no>'
Would you like to contribute anonymous usage statistics? [y/N]: y
Thanks for helping us! You can disable telemetry with the command 'crc config set consent-telemetry no'.
INFO Using bundle path C:\Users\crcqe\.crc\cache\crc_hyperv_4.18.2_amd64.crcbundle
INFO Checking minimum RAM requirements
INFO Check if Podman binary exists in: C:\Users\crcqe\.crc\bin\oc
INFO Checking if running in a shell with administrator rights
INFO Checking Windows release
INFO Checking Windows edition
INFO Checking if Hyper-V is installed and operational
INFO Checking if Hyper-V service is enabled
INFO Checking if crc-users group exists
INFO Checking if current user is in crc-users and Hyper-V admins group
INFO Checking if vsock is correctly configured
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if C:\Users\crcqe\.crc\cache\crc_hyperv_4.18.2_amd64.crcbundle exists
INFO Checking if the win32 background launcher is installed
INFO Checking if the daemon task is installed
INFO Installing the daemon task
INFO Checking if the daemon task is running
INFO Running the daemon task
Temporary error: daemon is not running yet (x8)

running crc daemon --log-level debug on windows is failing with following error:

PS C:\Users\rhqp> crc daemon --log-level debug
DEBU CRC version: 2.50.0+8caa80
DEBU OpenShift version: 4.18.2
DEBU MicroShift version: 4.18.2
DEBU Running 'crc daemon'
INFO listening \\.\pipe\crc-http
INFO listening vsock://00000400-FACB-11E6-BD58-64006A7986D3
0B sent to the VM, 0B received from the VM
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x7ff6934791d6]

goroutine 92 [running]:
github.com/crc-org/crc/v2/cmd/crc/cmd.run.func4()
        D:/a/crc/crc/cmd/crc/cmd/daemon.go:221 +0x56
created by github.com/crc-org/crc/v2/cmd/crc/cmd.run in goroutine 1
        D:/a/crc/crc/cmd/crc/cmd/daemon.go:212 +0x345
@gbraad
Copy link
Contributor
gbraad commented May 20, 2025 •
edited
Loading

INFO Running the daemon task
Temporary error: daemon is not running yet (x8)

  • Can you look at what the eventviewer says ?
  • What about the state of the service in services.msc (or was it 'task scheduler' ?

@anjannath anjannath changed the title [bug] crc setup fail on windows [bug] crc setup fail on windows as crc daemon hits panic to invalid pointer reference May 20, 2025
@gbraad
Copy link
Contributor
gbraad commented May 20, 2025 •
edited
Loading 
goroutine 92 [running]:
github.com/crc-org/crc/v2/cmd/crc/cmd.run.func4()
        D:/a/crc/crc/cmd/crc/cmd/daemon.go:221 +0x56
created by github.com/crc-org/crc/v2/cmd/crc/cmd.run in goroutine 1
        D:/a/crc/crc/cmd/crc/cmd/daemon.go:212 +0x345

crc/cmd/crc/cmd/daemon.go

Lines 212 to 227 in 8caa80f

go func() {
var oldCancel context.CancelFunc
for {
ctx, cancel := context.WithCancel(context.Background())
conn, err := unixgramListener(ctx, vn)
if err != nil && !errors.Is(err, net.ErrClosed) {
logging.Errorf("unixgramListener error: %v", err)
}
if oldCancel != nil {
logging.Warnf("New connection from %s. Closing old connection", conn.LocalAddr().String())
oldCancel()
}
oldCancel = cancel
time.Sleep(1 * time.Second)
}
}()

I wonder what would fail here... but it is at least related to a recent change: b68cd80

@gbraad gbraad mentioned this issue May 20, 2025
Merged
12 tasks
@gbraad gbraad linked a pull request May 20, 2025 that will close this issue
Return ErrNotImplemented from unixgramListener on windows and linux #4765
Merged
12 tasks
@vyasgun vyasgun self-assigned this May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vyasgun vyasgun

Labels
None yet
Projects
Project planning: crc
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Return ErrNotImplemented from unixgramListener on windows and linux vyasgun/crc
4 participants
@gbraad @anjannath @vyasgun @lilyLuLiu
0