MySql my.ini 修改存储位置

原创于 2023-01-05 11:20:26 发布 · 298 阅读

·

0

·

0 ·

CC 4.0 BY-SA版权

文章标签：

#mysql

该文章描述了如何在编码为ANSI的环境中，找到并修改MySQL的datadir配置，安全地将数据库中的数据移动到新路径下，并在操作完成后重启MySQL服务以确保更改生效。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

找到datadir 修改。

编码 ANSI。

如果数据库有数据把原数据位置下的数据都移到的新的路径下。

重启mysql服务

TheRulingPower

博客等级

码龄9年

17
原创

70
点赞

93
收藏

43
粉丝

关注

私信

最新评论

Ubuntu 22.04搭建 K8S 1.29+Calicao网络+Kuboard 超详细
niumowang2021: 你这篇文章没有安装cni-plugins
Ubuntu 22.04搭建 K8S 1.29+Calicao网络+Kuboard 超详细
niumowang2021: Warning FailedScheduling 18m (x2 over 23m) default-scheduler 0/3 nodes are available: 3 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling. Normal Scheduled 16m default-scheduler Successfully assigned calico-system/calico-kube-controllers-7cb98f8d4f-48jwx to k8s-master Warning NetworkNotReady 11m (x152 over 16m) kubelet network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Warning NetworkNotReady 82s (x301 over 11m) kubelet network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
Ubuntu 22.04搭建 K8S 1.29+Calicao网络+Kuboard 超详细
齐柏林fly 艇: 初始化失败
Ubuntu 22.04搭建 K8S 1.29+Calicao网络+Kuboard 超详细
齐柏林fly 艇: root@k8s-master:/# kubeadm init --config kubeadm-config.yaml [init] Using Kubernetes version: v1.29.0 [preflight] Running pre-flight checks [WARNING Hostname]: hostname "node" could not be reached [WARNING Hostname]: hostname "node": lookup node on 127.0.0.53:53: server misbehaving [preflight] Pulling images required for setting up a Kubernetes cluster [preflight] This might take a minute or two, depending on the speed of your internet connection [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
Ubuntu 22.04搭建 K8S 1.29+Calicao网络+Kuboard 超详细
mstrig: Unfortunately, an error has occurred: timed out waiting for the condition This error is likely caused by: - The kubelet is not running - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: - 'systemctl status kubelet' - 'journalctl -xeu kubelet' Additionally, a control plane component may have crashed or exited when started by the container runtime. To troubleshoot, list all containers using your preferred container runtimes CLI. Here is one example how you may list all running Kubernetes containers by using crictl: - 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause' Once you have found the failing container, you can inspect its logs with: - 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock