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

Error during installation: waiting for MongoDB to be ready… Error: signal: killed. #4790

Closed
zhubao315 opened this issue Jun 21, 2024 · 2 comments
Labels
kind/bug Something isn't working response-expired

Comments

@zhubao315
Copy link

Sealos Version

v5.0.0-beta5

How to reproduce the bug?

Error during installation
waiting for mongodb secret generated
waiting for mongodb ready ...Error: signal: killed

Installation steps

curl -sfL https://mirror.ghproxy.com/https://raw.githubusercontent.com/labring/sealos/v5.0.0-beta5/scripts/cloud/install.sh -o /tmp/install.sh && bash /tmp/install.sh \
--cloud-version=v5.0.0-beta5 \
--image-registry=registry.cn-shanghai.aliyuncs.com --zh \
--proxy-prefix=https://mirror.ghproxy.com



Master IP:192.168.1.80
Node IP:192.168.1.81,192.168.1.83
Domain name:192.168.1.80.nip.io

MongoDB 5.0版本依赖支持 AVX 指令集的 CPU, 当前环境不支持 AVX, 已切换为 MongoDB 4.0版本, 更多信息查看: https://www.mongodb.com/docs/v5.0/administration/production-notes/
2024-06-20T18:56:19 info start to install app in this cluster
2024-06-20T18:56:19 info Executing SyncStatusAndCheck Pipeline in InstallProcessor
2024-06-20T18:56:19 info Executing ConfirmOverrideApps Pipeline in InstallProcessor
2024-06-20T18:56:19 info Executing PreProcess Pipeline in InstallProcessor
2024-06-20T18:56:20 info Executing pipeline MountRootfs in InstallProcessor.
2024-06-20T18:58:01 info Executing pipeline MirrorRegistry in InstallProcessor.
2024-06-20T18:58:01 info Executing UpgradeIfNeed Pipeline in InstallProcessor
namespace/sealos-system created
namespace/sealos created
customresourcedefinition.apiextensions.k8s.io/notifications.notification.sealos.io created
no mongodb uri found, create mongodb and gen mongodb uri
waiting for mongodb secret generated
waiting for mongodb ready ...Error: signal: killed


### What is the expected behavior?

_No response_

### What do you see instead?

kubectl get pods -A
NAMESPACE                   NAME                                                              READY   STATUS    RESTARTS       AGE
cert-manager                cert-manager-5f8646db6b-5nhxh                                     1/1     Running   0              14h
cert-manager                cert-manager-cainjector-5cf5f57dd7-fdmp6                          1/1     Running   0              14h
cert-manager                cert-manager-webhook-687b7f8b97-l5txj                             1/1     Running   0              14h
cockroach-operator-system   cockroach-operator-manager-848fd7d88d-zpnk4                       1/1     Running   0              14h
ingress-nginx               ingress-nginx-controller-26dpm                                    1/1     Running   0              14h
ingress-nginx               ingress-nginx-controller-6n9mw                                    1/1     Running   0              14h
ingress-nginx               ingress-nginx-controller-wb5d9                                    1/1     Running   0              14h
kb-system                   kb-addon-snapshot-controller-64b4dcb6bc-lzfdm                     1/1     Running   2 (14h ago)    14h
kb-system                   kubeblocks-6954875d7d-rtcnh                                       1/1     Running   3 (14h ago)    14h
kb-system                   kubeblocks-dataprotection-5cfdf54fcc-zh7wg                        1/1     Running   4 (14h ago)    14h
kube-system                 cilium-gpgmh                                                      1/1     Running   0              14h
kube-system                 cilium-gplkj                                                      1/1     Running   0              14h
kube-system                 cilium-jtf27                                                      1/1     Running   0              14h
kube-system                 cilium-operator-97f465f54-lrktg                                   1/1     Running   4 (14h ago)    14h
kube-system                 coredns-5d78c9869d-8mxzp                                          1/1     Running   0              14h
kube-system                 coredns-5d78c9869d-kppdj                                          1/1     Running   0              14h
kube-system                 etcd-rofine30                                                     1/1     Running   2              14h
kube-system                 kube-apiserver-rofine30                                           1/1     Running   2              14h
kube-system                 kube-controller-manager-rofine30                                  1/1     Running   10 (14h ago)   14h
kube-system                 kube-proxy-5mkgv                                                  1/1     Running   0              14h
kube-system                 kube-proxy-82k5f                                                  1/1     Running   0              14h
kube-system                 kube-proxy-kvnxl                                                  1/1     Running   0              14h
kube-system                 kube-scheduler-rofine30                                           1/1     Running   10 (14h ago)   14h
kube-system                 kube-sealos-lvscare-rofine31                                      1/1     Running   1              14h
kube-system                 kube-sealos-lvscare-rofine32                                      1/1     Running   1              14h
kube-system                 metrics-server-84c9bd846f-hb8sh                                   1/1     Running   0              14h
openebs                     openebs-localpv-provisioner-6b456b4c69-wxxr8                      1/1     Running   4 (14h ago)    14h
vm                          victoria-metrics-k8s-stack-grafana-55b778cbf9-jnbsb               3/3     Running   0              14h
vm                          victoria-metrics-k8s-stack-kube-state-metrics-658d9b4dd5-tglth    1/1     Running   0              14h
vm                          victoria-metrics-k8s-stack-prometheus-node-exporter-scbzm         1/1     Running   0              14h
vm                          victoria-metrics-k8s-stack-prometheus-node-exporter-sd7tw         1/1     Running   0              14h
vm                          victoria-metrics-k8s-stack-prometheus-node-exporter-vmglj         1/1     Running   0              14h
vm                          victoria-metrics-k8s-stack-victoria-metrics-operator-6b774mjx9v   1/1     Running   3 (14h ago)    14h
vm                          vmagent-victoria-metrics-k8s-stack-c694d459d-vsxxm                2/2     Running   0              14h
vm                          vmalert-victoria-metrics-k8s-stack-695868d7fc-89vr8               2/2     Running   0              14h
vm                          vmalertmanager-victoria-metrics-k8s-stack-0                       2/2     Running   0              14h
vm                          vmsingle-victoria-metrics-k8s-stack-687d8cc7b4-r6c6d              1/1     Running   0              14h


### Operating environment

```markdown
- Sealos version: v5.0.0-beta5
- Docker version: containerd://1.7.15
- Kubernetes version: v1.27.11
- Operating system: Anolis OS 8.9   5.10.134-16.2.an8.x86_64
- Runtime environment:
- Cluster size:
- Additional information:

Additional information

No response

@zhubao315 zhubao315 added the kind/bug Something isn't working label Jun 21, 2024
@zhubao315
Copy link
Author

手工修改安装脚本,把mongodb版本 改为 4.4

vi /tmp/install.sh

#TODO mongo 5.0 need avx support, if not support, change to 4.0
setMongoVersion() {
set +e
grep avx /proc/cpuinfo > /dev/null 2>&1
if [ $? -ne 0 ]; then
get_prompt "mongo_avx_requirement"
mongodb_version="mongodb-4.4"
fi
set -e
}

重新安装,问题解决

bash /tmp/install.sh
--cloud-version=v5.0.0-beta5
--image-registry=registry.cn-shanghai.aliyuncs.com --zh
--proxy-prefix=https://mirror.ghproxy.com

Copy link

stale bot commented Aug 22, 2024

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

@stale stale bot closed this as completed Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working response-expired
Projects
None yet
Development

No branches or pull requests

1 participant