Skip to content
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.

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

install error #1093

Open
nikoxp opened this issue Mar 20, 2025 · 5 comments
Open

install error #1093

nikoxp opened this issue Mar 20, 2025 · 5 comments

Comments

@nikoxp
Copy link

nikoxp commented Mar 20, 2025

clusterconfiguration.installer.kubesphere.io/ks-installer created
2025-03-20T13:38:28.639+0800 [A] dp-olares78: ApplyKsInstaller success (1m10.082318476s)
2025-03-20T13:38:28.640+0800 [Module] DeployKsPlugins
2025-03-20T13:38:30.524+0800 [A] dp-olares78: CheckNodeState success (1.884380103s)
namespace/kubesphere-controls-system created
namespace/kubesphere-monitoring-federated created
namespace/default labeled
namespace/default labeled
namespace/kube-node-lease labeled
namespace/kube-node-lease labeled
namespace/kube-public labeled
namespace/kube-public labeled
namespace/kube-system labeled
namespace/kube-system labeled
namespace/kubekey-system labeled
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?
2025-03-20T13:40:25.075+0800 label ns kubekey-system kubesphere.io/namespace=kubekey-system failed: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl label ns kubekey-system kubesphere.io/namespace=kubekey-system --overwrite
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: exit status 1
2025-03-20T13:40:25.075+0800 dp-olares78 label namespace kubekey-system kubesphere.io/namespace=kubekey-system failed: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl label ns kubekey-system kubesphere.io/namespace=kubekey-system --overwrite
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: exit status 1: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl label ns kubekey-system kubesphere.io/namespace=kubekey-system --overwrite
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: exit status 1
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?
2025-03-20T13:40:32.029+0800 create ns kubesphere-controls-system failed: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: exit status 1
2025-03-20T13:40:32.029+0800 dp-olares78 create namespace kubesphere-controls-system failed: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: exit status 1: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?: exit status 1
Error from server (ServiceUnavailable): the server is currently unable to handle the request (post namespaces)
2025-03-20T13:40:41.240+0800 create ns kubesphere-controls-system failed: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
Error from server (ServiceUnavailable): the server is currently unable to handle the request (post namespaces): exit status 1
2025-03-20T13:40:41.241+0800 dp-olares78 create namespace kubesphere-controls-system failed: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
Error from server (ServiceUnavailable): the server is currently unable to handle the request (post namespaces): exit status 1: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
Error from server (ServiceUnavailable): the server is currently unable to handle the request (post namespaces): exit status 1
2025-03-20T13:40:41.241+0800 [A] dp-olares78: InitKsNamespace failed (2m10.716578609s)
2025-03-20T13:40:41.243+0800 [Job] [Install the System] execute failed
2025/03/20 13:40:41 error: Module[DeployKsPlugins] exec failed:
failed - dp-olares78: [A] InitKsNamespace: InitKsNamespace exec failed after 3 retires: create namespace kubesphere-controls-system failed: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
Error from server (ServiceUnavailable): the server is currently unable to handle the request (post namespaces): exit status 1: Failed to exec command: /bin/bash -c /usr/local/bin/kubectl create ns kubesphere-controls-system
Error from server (ServiceUnavailable): the server is currently unable to handle the request (post namespaces): exit status 1

@eball
Copy link
Collaborator

eball commented Mar 20, 2025

Could you please provide more information like the OS version, Olares version, etc.

Could you please try to execute the command

journalctl -u k3s > k3s.log

and provide us the file k3s.log

THX

@nikoxp
Copy link
Author

nikoxp commented Mar 20, 2025

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
─────────────────────────────────────────────────────
DietPi v9.11.2 : 16:53 - Wed 03/19/25
─────────────────────────────────────────────────────

  • Device model : Virtual Machine (x86_64)

run command:
curl -fsSL https://olares.sh | bash -

Olares version: v1.11.5

k3s.log

@dkeven
Copy link
Contributor

dkeven commented Mar 20, 2025

hi @nikoxp , based on the logs you provided, it's obvious that the Kubernetes system is suffering from a very slow I/O, to the extent that it can not even operate normally on its own, not to say install Olares upon it (the installation of Olares has not started yet).

what disk are you using? and what's its I/O performance? For the normal operation of Kubernetes, we recommend you use a SSD, or refer to the hardware requirements of ETCD (it's the backing database for Kubernetes)

@nikoxp
Copy link
Author

nikoxp commented Mar 21, 2025

my hardware:
128G SSD,4CPU,16Gmem,use Virtual Machine ESXI

@dkeven
Copy link
Contributor

dkeven commented Mar 21, 2025

my hardware: 128G SSD,4CPU,16Gmem,use Virtual Machine ESXI

There could be various reasons, e.g., maybe the virtualization layer is causing an I/O delay, or other processes are putting pressure on the disk, or a hardware issue.

But for what it's worth, you can do a simple test of the I/O performance on both guest and host OS, like: fio --rw=write --ioengine=sync --fdatasync=1 --directory=. --size=40m --bs=4096 --name=test

On Debian-based systems, you can install it by sudo apt-get install -y fio

The IOPS, bandwidth and fdatasync latency stats will be reported when the test ends.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants