.mysql secret在哪_/root/.mysql_secret: No such file or directory

Installing MySQL system tables...2020-02-18 00:51:06 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for moredetails).2020-02-18 00:51:06 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.2020-02-18 00:51:06 0 [Note] ./bin/mysqld (mysqld 5.6.38-ndb-7.3.19-cluster-gpl) starting as process 1755...2020-02-18 00:51:06 1755[Note] InnoDB: Using atomics to ref count buffer pool pages2020-02-18 00:51:06 1755[Note] InnoDB: The InnoDB memory heap is disabled2020-02-18 00:51:06 1755[Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins2020-02-18 00:51:06 1755[Note] InnoDB: Memory barrier is not used2020-02-18 00:51:06 1755 [Note] InnoDB: Compressed tables use zlib 1.2.3

2020-02-18 00:51:06 1755[Note] InnoDB: Using Linux native AIO2020-02-18 00:51:06 1755[Note] InnoDB: Using CPU crc32 instructions2020-02-18 00:51:06 1755 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2020-02-18 00:51:06 1755[Note] InnoDB: Completed initialization of buffer pool2020-02-18 00:51:07 1755 [Note] InnoDB: Highest supported fileformat is Barracuda.2020-02-18 00:51:07 1755 [Note] InnoDB: 128rollback segment(s) are active.2020-02-18 00:51:07 1755 [Note] InnoDB: Waiting forpurge to start2020-02-18 00:51:07 1755 [Note] InnoDB: 5.6.38 started; log sequence number 1626007

2020-02-18 00:51:08 1755[Note] Binlog end2020-02-18 00:51:08 1755[Note] InnoDB: FTS optimize thread exiting.2020-02-18 00:51:08 1755[Note] InnoDB: Starting shutdown...2020-02-18 00:51:10 1755 [Note] InnoDB: Shutdown completed; log sequence number 1626017OK

Filling help tables...2020-02-18 00:51:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for moredetails).2020-02-18 00:51:10 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.2020-02-18 00:51:10 0 [Note] ./bin/mysqld (mysqld 5.6.38-ndb-7.3.19-cluster-gpl) starting as process 1778...2020-02-18 00:51:10 1778[Note] InnoDB: Using atomics to ref count buffer pool pages2020-02-18 00:51:10 1778[Note] InnoDB: The InnoDB memory heap is disabled2020-02-18 00:51:10 1778[Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins2020-02-18 00:51:10 1778[Note] InnoDB: Memory barrier is not used2020-02-18 00:51:10 1778 [Note] InnoDB: Compressed tables use zlib 1.2.3

2020-02-18 00:51:10 1778[Note] InnoDB: Using Linux native AIO2020-02-18 00:51:10 1778[Note] InnoDB: Using CPU crc32 instructions2020-02-18 00:51:10 1778 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2020-02-18 00:51:10 1778[Note] InnoDB: Completed initialization of buffer pool2020-02-18 00:51:10 1778 [Note] InnoDB: Highest supported fileformat is Barracuda.2020-02-18 00:51:10 1778 [Note] InnoDB: 128rollback segment(s) are active.2020-02-18 00:51:10 1778 [Note] InnoDB: Waiting forpurge to start2020-02-18 00:51:10 1778 [Note] InnoDB: 5.6.38 started; log sequence number 1626017

2020-02-18 00:51:10 1778[Note] Binlog end2020-02-18 00:51:10 1778[Note] InnoDB: FTS optimize thread exiting.2020-02-18 00:51:10 1778[Note] InnoDB: Starting shutdown...2020-02-18 00:51:12 1778 [Note] InnoDB: Shutdown completed; log sequence number 1626027OK

To start mysqld at boottimeyou have to copy

support-files/mysql.server to the right place foryour system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER!Todo so, start the server, thenissue the following commands:

./bin/mysqladmin -u root password 'new-password'

./bin/mysqladmin -u root -h mysql1 password 'new-password'Alternatively you can run:

./bin/mysql_secure_installationwhichwill also give you the option of removing the test

databases and anonymous user created by default. This is

strongly recommendedforproduction servers.

See the manualfor moreinstructions.

You can start the MySQL daemon with:

cd . ; ./bin/mysqld_safe &You can test the MySQL daemon with mysql-test-run.pl

cd mysql-test ; perl mysql-test-run.pl

Please report any problems at http://bugs.mysql.com/

The latest information about MySQL is available on the web at

http://www.mysql.com

Support MySQL by buying support/licenses at http://shop.mysql.com

WARNING: Found existing configfile ./my.cnf on the system.

Because thisfile might be inuse, it was not replaced,

but was usedin bootstrap (unless you used --defaults-file)

and when you later start the server.

The new default configfile was created as ./my-new.cnf,

please compare it with yourfile and take the changes you need.

这个错误是由于无法连接到本地主机的10248端口导致的。这个端口通常是kubelet进程监听的端口,用于健康检查。出现这个错误可能是由于kubelet进程没有正确启动或者配置错误导致的。 解决这个问题的方法是检查kubelet进程的状态和配置。你可以按照以下步骤进行操作: 1. 检查kubelet进程是否正在运行。你可以使用以下命令检查kubelet进程的状态: ```shell systemctl status kubelet ``` 如果kubelet进程没有运行,你可以使用以下命令启动它: ```shell systemctl start kubelet ``` 2. 检查kubelet的配置文件。你可以使用以下命令查看kubelet的配置文件路径: ```shell kubelet --kubeconfig /etc/kubernetes/kubelet.conf --config /var/lib/kubelet/config.yaml --bootstrap-kubeconfig /etc/kubernetes/bootstrap-kubelet.conf config view ``` 确保配置文件中的端口号和地址正确,并且与你的环境相匹配。 3. 检查网络连接。你可以使用以下命令检查是否可以连接到localhost的10248端口: ```shell curl -sSL http://localhost:10248/healthz ``` 如果无法连接,请确保端口没有被防火墙或其他网络配置阻止。 4. 检查docker的配置。有时候,kubelet进程依赖于docker进程。你可以按照以下步骤检查docker的配置: - 创建/etc/docker目录: ```shell sudo mkdir /etc/docker ``` - 编辑/etc/docker/daemon.json文件,并添加以下内容: ```json { "exec-opts": ["native.cgroupdriver=systemd"], "log-driver": "json-file", "log-opts": { "max-size": "100m" }, "storage-driver": "overlay2", "storage-opts": [ "overlay2.override_kernel_check=true" ], "registry-mirrors": ["https://tdhp06eh.mirror.aliyuncs.com"] } ``` - 重启docker进程: ```shell systemctl restart docker ``` 请注意,以上步骤是一种常见的解决方法,但具体解决方法可能因环境而异。如果以上步骤无法解决问题,请提供更多的错误信息和环境配置,以便我们能够更好地帮助你。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值