Docker Desktop not starting possible elevated privileges issue - windows

When I launch Docker Desktop. I cannot see it in the taskbar or the system tray.
I can see it running as a background process in task manager.
I try to run the diagnose it is
[2022-11-11T12:05:32.437862000Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[SKIP] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x1c1 pc=0x15ff2f1]
goroutine 1 [running]:
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.findStringInKMSG({0xc000629140?, 0xc000438680?})
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/vm.go:54 +0x51
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.vmStartWorks()
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/vm.go:40 +0x25
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1d43f60)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.Run.func1(0x1d43f60)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x6?, 0x1d43f60)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x5, 0x1d43f60, 0xc00061f728)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x4, 0x1d43fe0, 0xc00061f728)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x1d440e0, 0xc00061f728)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1d44160, 0xc00061f728)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1d441e0, 0xc00061f728)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1d44960, 0xc00061f728)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkOnce(0x16e29c0?, 0xc00035f890)
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.Run(0x1d44960, 0xaa0fd02800000010?, {0xc00035fb20, 0x1, 0x1})
github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
main.checkCmd({0xc0000743d0?, 0xc0000743d0?, 0x4?}, {0x0, 0x0})
github.com/docker/pinata/common/cmd/com.docker.diagnose/main.go:133 +0x105
main.main()
github.com/docker/pinata/common/cmd/com.docker.diagnose/main.go:99 +0x287
also the docker client can't connect
PS C:\Program Files\Docker\Docker\resources> docker version
error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version": open //./pipe/docker_engine: The system cannot find the file specified.
Client:
Cloud integration: v1.0.29
Version: 20.10.21
API version: 1.41
Go version: go1.18.7
Git commit: baeda1f
Built: Tue Oct 25 18:08:16 2022
OS/Arch: windows/amd64
Context: default
Experimental: true
I tried to run:
$ & 'C:\Program Files\Docker\Docker\DockerCli.exe' -SwitchDaemon
from a different stack overflow answer but didn't work.

Related

Docker desktop (WSL2 engine) fails to start after switching to windows containers on Windows 11 Home

I am on Windows 11 Home Edition (21H2). Installed docker desktop 4.15.0 from https://docs.docker.com/desktop/install/windows-install/. After installation everything seemed to work fine. I was able to run docker run hello-world from powershell. But then I wanted to build a Dockerfile that used the microsoft image mcr.microsoft.com/windows/servercore:ltsc2019
> docker build .
[...]
=> ERROR [internal] load metadata for mcr.microsoft.com/windows/servercore:ltsc2019 0.2s
------
> [internal] load metadata for mcr.microsoft.com/windows/servercore:ltsc2019:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest sha256:058c8482946efa0b44b57e5ecebd7857b4df37a1365acdde32736628747ad9e1: not found
I searched documentation, see https://docs.docker.com/desktop/faqs/windowsfaqs/#how-do-i-switch-between-windows-and-linux-containers :
From the Docker Desktop menu, you can toggle which daemon (Linux or Windows) the Docker CLI talks to. Select Switch to Windows containers to use Windows containers, [...]
I followed this instruction to switch to Windows containers:
But after selecting "Switch" button (see screenshot above), docker desktop just says "Docker desktop starting..." and nothing happens.
I checked the documentation again: https://docs.docker.com/desktop/troubleshoot/overview/ and ran the diagnostic tool:
> 'C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe' check
[2022-12-19T00:09:41.668707400Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-12-19T00:09:43.462307800Z][com.docker.diagnose.exe][I] ipc.NewClient: 5abd4d00-diagnose -> \\.\pipe\dockerDiagnosticd diagnosticsd
[common/pkg/diagkit/gather/diagnose.glob..func14()
[ common/pkg/diagkit/gather/diagnose/linuxkit.go:18 +0x8b
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x10140c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10140c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x10140c0)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x10140c0, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1014140, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10141c0, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1014940, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x9b2c80?, 0xc00026f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1014940, 0x3a35893600000010?, {0xc00026fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0000703d0?, 0xc0000703d0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-12-19T00:09:43.462865700Z][com.docker.diagnose.exe][I] (d1ae4863) 5abd4d00-diagnose C->S diagnosticsd GET /ping
[2022-12-19T00:09:43.463587400Z][com.docker.diagnose.exe][W] (d1ae4863) 5abd4d00-diagnose C<-S NoResponse GET /ping (548.7µs): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[FAIL] DD0023: is the Containers Windows Feature enabled? required Windows Feature not installed: Containers
[2022-12-19T00:09:43.465829700Z][com.docker.diagnose.exe][I] ipc.NewClient: b5ee5ef6-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service.exe
[common/pkg/windows/serviceclient.NewClientForPath(...)
[ common/pkg/windows/serviceclient/service.go:49
[common/pkg/windows/serviceclient.NewClient({0xa768bf, 0x13}, {0x0, 0x0, 0x0})
[ common/pkg/windows/serviceclient/service.go:38 +0xc5
[common/pkg/diagkit/gather/diagnose.checkWindowsFeature({{0xa6e7d9?, 0x1?}, {0xa6e7d9?, 0x8d?}})
[ common/pkg/diagkit/gather/diagnose/features_windows.go:11 +0x51
[common/pkg/diagkit/gather/diagnose.glob..func6()
[ common/pkg/diagkit/gather/diagnose/dockerd_windows.go:11 +0x35
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x10142c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10142c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x10142c0)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x10142c0, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1014140, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10141c0, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1014940, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x9b2c80?, 0xc00026f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1014940, 0x3a35893600000010?, {0xc00026fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0000703d0?, 0xc0000703d0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-12-19T00:09:43.465829700Z][com.docker.diagnose.exe][I] (d93b6fc4) b5ee5ef6-com.docker.diagnose C->S com.docker.service.exe POST /windowsfeatures/check: [Containers (Containers)]
[2022-12-19T00:09:43.939061900Z][com.docker.diagnose.exe][I] (d93b6fc4) b5ee5ef6-com.docker.diagnose C<-S 5523a302-ServiceAPI POST /windowsfeatures/check (473.2322ms): {"NotAvailable":[{"Description":"Containers","Name":"Containers"}],"NotEnabled":[]}
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:43.940262800Z][com.docker.diagnose.exe][I] ipc.NewClient: a1bc4120-com.docker.diagnose -> \\.\pipe\dockerLifecycleServer VMDockerdAPI
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...)
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:61
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0xa768bf, 0x13})
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:55 +0x99
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1014140)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1014140)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x3?, 0x1014140)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1014140, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10141c0, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1014940, 0xc00061f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x9b2c80?, 0xc00026f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1014940, 0x3a35893600000010?, {0xc00026fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0000703d0?, 0xc0000703d0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-12-19T00:09:43.940869400Z][com.docker.diagnose.exe][I] (0277e282) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-12-19T00:09:43.941441100Z][com.docker.diagnose.exe][W] (0277e282) a1bc4120-com.docker.diagnose C<-S NoResponse GET /docker (571.7µs): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:43.942116600Z][com.docker.diagnose.exe][I] (0277e282-1) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:43.942116600Z][com.docker.diagnose.exe][W] (0277e282-1) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:44.951299700Z][com.docker.diagnose.exe][I] (0277e282-2) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:44.952368100Z][com.docker.diagnose.exe][W] (0277e282-2) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (1.0684ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:45.966443900Z][com.docker.diagnose.exe][I] (0277e282-3) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:45.967076400Z][com.docker.diagnose.exe][W] (0277e282-3) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (632.5µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:46.978045300Z][com.docker.diagnose.exe][I] (0277e282-4) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:46.979132400Z][com.docker.diagnose.exe][W] (0277e282-4) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (1.2815ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:47.984015000Z][com.docker.diagnose.exe][I] (0277e282-5) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:47.985051200Z][com.docker.diagnose.exe][W] (0277e282-5) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (1.0362ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:48.991994000Z][com.docker.diagnose.exe][I] (0277e282-6) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:48.993515900Z][com.docker.diagnose.exe][W] (0277e282-6) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (1.0491ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:49.999431800Z][com.docker.diagnose.exe][I] (0277e282-7) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:50.000430100Z][com.docker.diagnose.exe][W] (0277e282-7) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (998.3µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-12-19T00:09:51.020341400Z][com.docker.diagnose.exe][I] (0277e282-8) a1bc4120-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-12-19T00:09:51.021623100Z][com.docker.diagnose.exe][W] (0277e282-8) a1bc4120-com.docker.diagnose C<-S NoResponse GET /ping (1.2817ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0013: is the $PATH ok?
error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0005: is the user in the docker-users group?
2022/12/19 01:09:51 exit status 0xffffffff
From the above output I see:
[FAIL] DD0023: is the Containers Windows Feature enabled? required Windows Feature not installed: Containers
I tried to search the documentation for more information on this, but was not able to find any good advice. Any idea what is going on here?

emqx start command is not starting the mqtt broker

I am having an issue with running emqx.
When I run emqx start, It shows:
emqx v3.2.7 is started successfully!
When I run emx_ctl status:
Node 'emqx#127.0.0.1' not responding to pings.
When I run emqx console:
MacBook-Pro:bin apple$ emqx console
!!!!
!!!! WARNING: ulimit -n is 256; 1024 is the recommended minimum.
!!!!
Exec: /usr/local/Cellar/emqx/3.2.7/erts-10.3.5/bin/erlexec -boot /usr/local/Cellar/emqx/3.2.7/releases/v3.2.7/emqx -mode embedded -boot_var ERTS_LIB_DIR /usr/local/Cellar/emqx/3.2.7/erts-10.3.5/../lib -mnesia dir "/usr/local/Cellar/emqx/3.2.7/data/mnesia/emqx#127.0.0.1" -config /usr/local/Cellar/emqx/3.2.7/data/configs/app.2019.12.13.02.35.23.config -args_file /usr/local/Cellar/emqx/3.2.7/data/configs/vm.2019.12.13.02.35.23.args -vm_args /usr/local/Cellar/emqx/3.2.7/data/configs/vm.2019.12.13.02.35.23.args -- console
Root: /usr/local/Cellar/emqx/3.2.7
/usr/local/Cellar/emqx/3.2.7
Erlang/OTP 21 [erts-10.3.5] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:32] [hipe] [dtrace]
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypto}}},{kernel,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypto}}},{kernel,start,[normal,[]]}}})
Crash dump is being written to: log/crash.dump...done

How to dump goroutines stack race of the running kubelet

kubernetes is complicated, kubelet run into deadlocks after long running in some scenarios.
Is there a way to dump goroutine stack trace of the running kubelet?
The expected output like following which is very helpful to debug deadlock kind issues of kubelet.
goroutine 386 [chan send, 1140 minutes]:
k8s.io/kubernetes/pkg/kubelet/pleg.(*GenericPLEG).relist(0xc42069ea20)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubelet/pleg/generic.go:261 +0x74e
k8s.io/kubernetes/pkg/kubelet/pleg.(*GenericPLEG).(k8s.io/kubernetes/pkg/kubelet/pleg.relist)-fm()
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubelet/pleg/generic.go:130 +0x2a
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4212ee520)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x54
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4212ee520, 0x3b9aca00, 0x0, 0x1, 0xc420056540)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134 +0xbd
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4212ee520, 0x3b9aca00, 0xc420056540)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 +0x4d
created by k8s.io/kubernetes/pkg/kubelet/pleg.(*GenericPLEG).Start
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubelet/pleg/generic.go:130 +0x88
...
goroutine 309 [sleep]:
time.Sleep(0x12a05f200)
/usr/local/go/src/runtime/time.go:102 +0x166
k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoop(0xc4205e3b00, 0xc420ff2780, 0x3e56a60, 0xc4205e3b00)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubelet/kubelet.go:1777 +0x1e7
k8s.io/kubernetes/pkg/kubelet.(*Kubelet).Run(0xc4205e3b00, 0xc420ff2780)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubelet/kubelet.go:1396 +0x27f
k8s.io/kubernetes/cmd/kubelet/app.startKubelet.func1()
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubelet/app/server.go:998 +0x67
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc42105dfb0)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x54
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc42105dfb0, 0x0, 0x0, 0x1, 0xc420056540)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134 +0xbd
k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc42105dfb0, 0x0, 0xc420056540)
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 +0x4d
created by k8s.io/kubernetes/cmd/kubelet/app.startKubelet
/workspace/anago-v1.11.5-beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubelet/app/server.go:996 +0xea
...
I appreciate that anyone could share the experience about how to dump goroutines stack race of kubelet that something like what docker provided[1]
$ pkill -SIGUSR1 dockerd
[1]. https://success.docker.com/article/how-to-dump-goroutines-stacktraces
pprof, it will keep kubelet running
install go on node-x
run “kubectl proxy” in one terminal
curl http://localhost:8001/api/v1/proxy/nodes/node-x/debug/pprof/goroutine?debug=2
notes: API changed for different k8s versions, for 1.16 it's
curl http://127.0.0.1:8001/api/v1/nodes/node-**/proxy/debug/pprof/goroutine?debug=2
send signal to kubelet which caused kubelet to exit with a stack dump
kill -SIGABRT

hyperledger configtxgen error

I am actually trying to build two blockchains on two diffents VPS. The first one is working but after many hours of research, i didn't find why the second blockchain don't want to build.
I built the crypto-config folder, it is OK, but when I try to build the channel-artifacts folder it is not working and I have exactly the same approach. Here is the log :
2018-07-05 17:05:43.046 CEST [common/tools/configtxgen] main -> WARN 001 Omitting the channel ID for configtxgen is deprecated. Explicitly passing the channel ID will be required in the future, defaulting to 'testchainid'.
2018-07-05 17:05:43.046 CEST [common/tools/configtxgen] main -> INFO 002 Loading configuration
2018-07-05 17:05:43.046 CEST [common/tools/configtxgen/localconfig] Load -> CRIT 003 Error reading configuration: While parsing config: yaml: unknown anchor 'ChannelCapabilities' referenced
2018-07-05 17:05:43.047 CEST [common/tools/configtxgen] func1 -> CRIT 004 Error reading configuration: While parsing config: yaml: unknown anchor 'ChannelCapabilities' referenced
panic: Error reading configuration: While parsing config: yaml: unknown anchor 'ChannelCapabilities' referenced [recovered]
panic: Error reading configuration: While parsing config: yaml: unknown anchor 'ChannelCapabilities' referenced
goroutine 1 [running]:
github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panic(0xc420199e00, 0xc420414390, 0x1, 0x1)
/w/workspace/fabric-nightly-release-job-x86_64/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:188 +0xbd
main.main.func1()
/w/workspace/fabric-nightly-release-job-x86_64/gopath/src/github.com/hyperledger/fabric/common/tools/configtxgen/main.go:254 +0x1ae
panic(0xc6ed20, 0xc420414380)
/opt/go/go1.10.linux.amd64/src/runtime/panic.go:505 +0x229
github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panic(0xc420199c50, 0xc4201916a0, 0x2, 0x2)
/w/workspace/fabric-nightly-release-job-x86_64/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:188 +0xbd
github.com/hyperledger/fabric/common/tools/configtxgen/localconfig.Load(0x7ffdd627483b, 0x15, 0x0, 0x0, 0x0, 0x1)
/w/workspace/fabric-nightly-release-job-x86_64/gopath/src/github.com/hyperledger/fabric/common/tools/configtxgen/localconfig/config.go:277 +0x469
main.main()
/w/workspace/fabric-nightly-release-job-x86_64/gopath/src/github.com/hyperledger/fabric/common/tools/configtxgen/main.go:265 +0xce7
My configtx.yaml file is basically the same as the first-network with just the paths changed.
Any help?
This seems to be related to the 1.2.0 release. I was able to get CLI running again by downgrading to 1.1.0 (hyperledger/fabric-ca-tools:x86_64-1.1.0).
Ref: https://hub.docker.com/r/hyperledger/fabric-ca-tools/tags/
Edit: https://github.com/hyperledger/fabric/releases/tag/v1.2.0
My fix was to make sure the Organizations section is at the top. I think all you need to do is move the section containing &ChannelCapabilities higher in your configtx.yaml.

OpenJDK on FreeBSD: "Given reserved space must have been reserved already"

I'm trying to get Artifactory up and running on a FreeBSD machine. I installed /usr/ports/devel/artifactory, seemingly without problem, and then ran "/usr/local/etc/rc.d/artifactory start". It said Artifactory was starting, and didn't give any obvious signs of error, but when the script ended, Artifactory was not running. I found that every time I do this, the following is appended to /usr/local/artifactory/logs/boot.log:
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (g1PageBasedVirtualSpace.cpp:54), pid=87801, tid=100176
# guarantee(rs.is_reserved()) failed: Given reserved space must have been reserved already.
Googling that "Given reserved space must have been reserved already" reveals no information that is particularly useful to me. It seems to be a message from within the OpenJDK.
The log file also mentions that another file was created with more detailed error information. That file has a stack trace and various other info:
--------------- T H R E A D ---------------
Current thread (0x29cb0800): JavaThread "Unknown thread" [_thread_in_vm, id=100176, stack(0xbf9be000,0xbf9fe000)]
Stack: [0xbf9be000,0xbf9fe000], sp=0xbf9fd528, free space=253k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x8234ed] JVM_handle_bsd_signal+0x166bbd
V [libjvm.so+0x36ef3f] SUNWprivate_1.1+0x36ef3f
V [libjvm.so+0x40df4c] AsyncGetCallTrace+0x2c0bc
V [libjvm.so+0x40def4] AsyncGetCallTrace+0x2c064
V [libjvm.so+0x40ff0b] AsyncGetCallTrace+0x2e07b
V [libjvm.so+0x41017e] AsyncGetCallTrace+0x2e2ee
V [libjvm.so+0x3f5874] AsyncGetCallTrace+0x139e4
V [libjvm.so+0x7ea485] JVM_handle_bsd_signal+0x12db55
V [libjvm.so+0x7ea105] JVM_handle_bsd_signal+0x12d7d5
V [libjvm.so+0x471291] AsyncGetCallTrace+0x8f401
V [libjvm.so+0x7cccd3] JVM_handle_bsd_signal+0x1103a3
V [libjvm.so+0x4d0eeb] JNI_CreateJavaVM+0x6b
C [java+0x3c35] JavaMain+0x1d5
C [libthr.so.3+0x76dc] operator->+0x81c
C 0x00000000
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
Other Threads:
=>0x29cb0800 (exited) JavaThread "Unknown thread" [_thread_in_vm, id=100176, stack(0xbf9be000,0xbf9fe000)]
VM state:not at safepoint (not fully initialized)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x29c48640] Heap_lock - owner thread: 0x29cb0800
GC Heap History (0 events):
No events
Deoptimization events (0 events):
No events
Internal exceptions (0 events):
No events
Events (0 events):
No events
Dynamic libraries:
0x08048000 /usr/local/openjdk8/bin/java
0x2807d000 /lib/libz.so.6
0x28091000 /lib/libthr.so.3
0x280b3000 /lib/libc.so.7
0x28c00000 /usr/local/openjdk8/jre/lib/i386/server/libjvm.so
0x28237000 /lib/libm.so.5
0x2825d000 /usr/lib/libc++.so.1
0x2830c000 /lib/libcxxrt.so.1
0x28325000 /lib/libgcc_s.so.1
0x28331000 /usr/local/openjdk8/jre/lib/i386/libverify.so
0x2833d000 /usr/local/openjdk8/jre/lib/i386/libjava.so
0x2836a000 /usr/local/openjdk8/jre/lib/i386/libzip.so
0x28054000 /libexec/ld-elf.so.1
VM Arguments:
jvm_args: -Djava.util.logging.config.file=/usr/local/artifactory/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms512m -Xmx2g -Xss256k -XX:+UseG1GC -Djruby.compile.invokedynamic=false -Dfile.encoding=UTF8 -Dartdist=zip -Dartifactory.home=/usr/local/artifactory -Dfile.encoding=UTF8 -Djruby.compile.invokedynamic=false -Djava.endorsed.dirs=/usr/local/artifactory/tomcat/endorsed -Dcatalina.base=/usr/local/artifactory/tomcat -Dcatalina.home=/usr/local/artifactory/tomcat -Djava.io.tmpdir=/usr/local/artifactory/tomcat/temp
java_command: org.apache.catalina.startup.Bootstrap start
java_class_path (initial): /usr/local/artifactory/tomcat/bin/bootstrap.jar:/usr/local/artifactory/tomcat/bin/tomcat-juli.jar
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=/usr/local/openjdk8
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/nonexistent/bin
SHELL=/bin/csh
HOSTTYPE=FreeBSD
OSTYPE=FreeBSD
MACHTYPE=i386
Signal Handlers:
SIGSEGV: [libjvm.so+0x824280], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGBUS: [libjvm.so+0x824280], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGFPE: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGPIPE: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGXFSZ: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGILL: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGUSR1: SIG_DFL, sa_mask[0]=11111111011111110111111111111111, sa_flags=none
SIGUSR2: [libjvm.so+0x6b9fe0], sa_mask[0]=00000000000000000000000000000000, sa_flags=SA_RESTART|SA_SIGINFO
SIGHUP: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGINT: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGTERM: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGQUIT: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
--------------- S Y S T E M ---------------
OS:BSD
uname:FreeBSD 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 22:51:51 UTC 2014 root#releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
rlimit: STACK 65536k, CORE infinity, NPROC 5547, NOFILE 94860, AS infinity
load average:0.26 0.19 0.80
CPU:total 8 (4 cores per cpu, 1 threads per core) family 6 model 26 stepping 5, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, tsc, tscinvbit, tscinv
Memory: 4k page, physical 3372996k(2931288k free), swap 13807988388243963904k(13807988392538586972k free)
vm_info: OpenJDK Server VM (25.60-b23) for bsd-x86 JRE (1.8.0_60-b24), built on Nov 14 2015 17:53:51 by "bob" with gcc 4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)
time: Sat Nov 14 18:21:52 2015
elapsed time: 0 seconds (0d 0h 0m 0s)
All packages are up to date and compiled from source. All Java-related stuff is newly installed (along with Artifactory) and with unchanged, default configuration.
Any ideas? Thanks.
This seems to be an issue with memory allocation.
The default heap size defined in the Artifactory startup script is 2g, which is more than the maximal heap size which can be allocated by the JVM on a 32bit FreeBSD machine.
The solution in this case would be deacreasing the maximum heap size to ~1.5g.

Resources