MySQL服务启动异常:Failed to start MySQL Server. mysqld.service holdoff time over, scheduling restart.

MySQL服务启动异常

在这里插入图片描述

systemctl status mysqld
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since 二 2023-07-18 20:15:00 CST; 2min 19s ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 4357 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=1/FAILURE)
  Process: 4085 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)

7月 18 20:14:59 localhost.localdomain systemd[1]: Failed to start MySQL Server.
7月 18 20:14:59 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state.
7月 18 20:14:59 localhost.localdomain systemd[1]: mysqld.service failed.
7月 18 20:15:00 localhost.localdomain systemd[1]: mysqld.service holdoff time over, scheduling restart.
7月 18 20:15:00 localhost.localdomain systemd[1]: Stopped MySQL Server.
7月 18 20:15:00 localhost.localdomain systemd[1]: start request repeated too quickly for mysqld.service
7月 18 20:15:00 localhost.localdomain systemd[1]: Failed to start MySQL Server.
7月 18 20:15:00 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state.
7月 18 20:15:00 localhost.localdomain systemd[1]: mysqld.service failed.
systemctl start mysqld

Job for mysqld.service failed because the control process exited with error code. See “systemctl status mysqld.service” and “journalctl -xe” for details.

chown

chown是一个常用的Linux/Unix命令,用于改变文件或目录的所有者(owner)。它的主要作用是将文件或目录的所有权转移给指定的用户或用户组。

chown命令的语法如下:

chown [选项] 用户名:用户组 文件/目录
其中,常用的选项包括:

-R:递归地改变指定目录及其子目录下的文件和目录的所有权。
-c:只在执行改变所有权操作时显示提示信息。
-v:显示详细的操作信息。
使用chown命令,可以实现以下功能:

转移文件/目录的所有权:可以将文件/目录的所有者更改为其他用户。
chown 用户名 文件/目录
转移用户组所有权:可以将文件/目录的用户组更改为其他用户组。
chown :用户组 文件/目录
同时转移所有者和用户组所有权:可以将文件/目录的所有者和用户组同时更改为其他用户和用户组。
chown 用户名:用户组 文件/目录
递归改变文件/目录的所有权:通过添加 -R 选项,可以递归地改变指定目录及其子目录下的所有文件和目录的所有权。
chown -R 用户名:用户组 目录
chown命令常用于系统管理员或文件的所有者进行文件/目录的权限管理。它可以帮助确保合适的用户或用户组拥有适当的访问权限,并提高系统的安全性和可管理性。
使用chown授予目录里权限

chown mysql:mysql -R /var/lib/mysql
chown mysql -R /var/lib/mysql
systemctl start mysqld

Job for mysqld.service failed because the control process exited with error code. See “systemctl status mysqld.service” and “journalctl -xe” for details.
[root@localhost ~]# journalctl -xe
Then execute:
restorecon -v ‘/cdh/logs/mysqld.log’

                                                    Plugin catchall (17.1 confidence) suggests   
                                                  
                                                  If you believe that mysqld should be allowed append access on the mysqld.log file by default.
                                                  Then you should report this as a bug.
                                                  You can generate a local policy module to allow this access.
                                                  Do
                                                  allow this access for now by executing:
                                                  # ausearch -c 'mysqld' --raw | audit2allow -M my-mysqld
                                                  # semodule -i my-mysqld.pp

7月 18 20:24:15 localhost.localdomain setroubleshoot[11170]: failed to retrieve rpm info for /cdh/logs/mysqld.log
7月 18 20:24:15 localhost.localdomain setroubleshoot[11170]: SELinux is preventing /usr/sbin/mysqld from append access on the file /cdh/logs/mysqld.log. For complete SELinux messages run: sealert -l 4f2a
7月 18 20:24:15 localhost.localdomain python[11170]: SELinux is preventing /usr/sbin/mysqld from append access on the file /cdh/logs/mysqld.log.

                                                  *****  Plugin catchall_labels (83.8 confidence) suggests   *******************
                                                  
                                                  If you want to allow mysqld to have append access on the mysqld.log file
                                                  Then you need to change the label on /cdh/logs/mysqld.log
                                                  Do
                                                  # semanage fcontext -a -t FILE_TYPE '/cdh/logs/mysqld.log'
                                                  where FILE_TYPE is one of the following: NetworkManager_log_t, NetworkManager_tmp_t, abrt_tmp_t, abrt_upload_watch_tmp_t, abrt_var_cache_t, abrt_var_
                                                  Then execute:
                                                  restorecon -v '/cdh/logs/mysqld.log'


​ ***** Plugin catchall (17.1 confidence) suggests **************************

                                                  If you believe that mysqld should be allowed append access on the mysqld.log file by default.
                                                  Then you should report this as a bug.
                                                  You can generate a local policy module to allow this access.
                                                  Do
                                                  allow this access for now by executing:
                                                  # ausearch -c 'mysqld' --raw | audit2allow -M my-mysqld
                                                  # semodule -i my-mysqld.pp

lines 2190-2228/2228 (END)
Then execute:
restorecon -v ‘/cdh/logs/mysqld.log’

                                                  *****  Plugin catchall (17.1 confidence) suggests   **************************
                                                  
                                                  If you believe that mysqld should be allowed append access on the mysqld.log file by default.
                                                  Then you should report this as a bug.
                                                  You can generate a local policy module to allow this access.
                                                  Do
                                                  allow this access for now by executing:
                                                  # ausearch -c 'mysqld' --raw | audit2allow -M my-mysqld
                                                  # semodule -i my-mysqld.pp

7月 18 20:24:15 localhost.localdomain setroubleshoot[11170]: failed to retrieve rpm info for /cdh/logs/mysqld.log
7月 18 20:24:15 localhost.localdomain setroubleshoot[11170]: SELinux is preventing /usr/sbin/mysqld from append access on the file /cdh/logs/mysqld.log. For complete SELinux messages run: sealert -l 4f2a4ed9-4
7月 18 20:24:15 localhost.localdomain python[11170]: SELinux is preventing /usr/sbin/mysqld from append access on the file /cdh/logs/mysqld.log.

                                                  *****  Plugin catchall_labels (83.8 confidence) suggests   *******************
                                                  
                                                  If you want to allow mysqld to have append access on the mysqld.log file
                                                  Then you need to change the label on /cdh/logs/mysqld.log
                                                  Do
                                                  # semanage fcontext -a -t FILE_TYPE '/cdh/logs/mysqld.log'
                                                  where FILE_TYPE is one of the following: NetworkManager_log_t, NetworkManager_tmp_t, abrt_tmp_t, abrt_upload_watch_tmp_t, abrt_var_cache_t, abrt_var_log_t,
                                                  Then execute:
                                                  restorecon -v '/cdh/logs/mysqld.log'


​ ***** Plugin catchall (17.1 confidence) suggests **************************

                                                  If you believe that mysqld should be allowed append access on the mysqld.log file by default.
                                                  Then you should report this as a bug.
                                                  You can generate a local policy module to allow this access.
                                                  Do
                                                  allow this access for now by executing:
                                                  # ausearch -c 'mysqld' --raw | audit2allow -M my-mysqld
                                                  # semodule -i my-mysqld.pp

~
~
~
lines 2190-2228/2228 (END)
Then execute:
restorecon -v ‘/cdh/logs/mysqld.log’

                                                  *****  Plugin catchall (17.1 confidence) suggests   **************************
                                                  
                                                  If you believe that mysqld should be allowed append access on the mysqld.log file by default.
                                                  Then you should report this as a bug.
                                                  You can generate a local policy module to allow this access.
                                                  Do
                                                  allow this access for now by executing:
                                                  # ausearch -c 'mysqld' --raw | audit2allow -M my-mysqld
                                                  # semodule -i my-mysqld.pp

7月 18 20:24:15 localhost.localdomain setroubleshoot[11170]: failed to retrieve rpm info for /cdh/logs/mysqld.log
7月 18 20:24:15 localhost.localdomain setroubleshoot[11170]: SELinux is preventing /usr/sbin/mysqld from append access on the file /cdh/logs/mysqld.log. For complete SELinux messages run: sealert -l 4f2a
7月 18 20:24:15 localhost.localdomain python[11170]: SELinux is preventing /usr/sbin/mysqld from append access on the file /cdh/logs/mysqld.log.

                                                  *****  Plugin catchall_labels (83.8 confidence) suggests   *******************
                                                  
                                                  If you want to allow mysqld to have append access on the mysqld.log file
                                                  Then you need to change the label on /cdh/logs/mysqld.log
                                                  Do
                                                  # semanage fcontext -a -t FILE_TYPE '/cdh/logs/mysqld.log'
                                                  where FILE_TYPE is one of the following: NetworkManager_log_t, NetworkManager_tmp_t, abrt_tmp_t, abrt_upload_watch_tmp_t, abrt_var_cache_t, abrt_var_
                                                  Then execute:
                                                  restorecon -v '/cdh/logs/mysqld.log'


​ ***** Plugin catchall (17.1 confidence) suggests **************************

                                                  If you believe that mysqld should be allowed append access on the mysqld.log file by default.
                                                  Then you should report this as a bug.
                                                  You can generate a local policy module to allow this access.
                                                  Do
                                                  allow this access for now by executing:
                                                  # ausearch -c 'mysqld' --raw | audit2allow -M my-mysqld
                                                  # semodule -i my-mysqld.pp

重点错误信息:

7月 18 20:24:15 localhost.localdomain setroubleshoot[11170]: SELinux is preventing /usr/sbin/mysqld from append access on the file /cdh/logs/mysqld.log. For complete SELinux messages run: sealert -l 4f2a

SELinux(Security-Enhanced Linux)是一个安全增强的Linux安全模块,它提供了Linux系统级别的强制访问控制(MAC)机制。它的目标是通过附加强制访问控制机制,限制进程的权限,并提供更细粒度的访问控制来增强系统的安全性。

相对于传统的Linux访问控制方式(基于用户和权限的访问控制),SELinux引入了基于角色的访问控制和类型强制访问控制。它通过在内核中实施安全策略和访问规则来限制进程对资源的访问,并控制进程间的相互作用。

getenforce是一个用于查看SELinux当前状态的命令。它通常用于检查SELinux的执行模式,以确定SELinux是启用还是禁用,并获取其当前的执行级别。

getenforce

Enforcing

[root@localhost ~]# setenforce 0
[root@localhost ~]# sed -i 's/^SELINUX=.*/SELINUX=disabled/'  /etc/selinux/config
[root@localhost ~]# getenforce

Permissive

[root@localhost ~]# systemctl start mysqld
[root@localhost ~]# systemctl status mysqld

● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: active (running) since 二 2023-07-18 20:26:07 CST; 5s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 13063 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=0/SUCCESS)
Process: 13036 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
Main PID: 13066 (mysqld)
Tasks: 30
CGroup: /system.slice/mysqld.service
└─13066 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid

7月 18 20:26:06 localhost.localdomain systemd[1]: Starting MySQL Server…
7月 18 20:26:07 localhost.localdomain systemd[1]: Started MySQL Server.

-- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 16:01:55 localhost.localdomain mysql-systemd-start[12907]: 2025-06-19 16:01:55 0 [Note] / usr/sbin/mysqld (mysqld 5.6.51) starting as process 12930 ... 6月 19 16:01:55 localhost.localdomain mysql-systemd-start[12907]: 2025-06-19 16:01:55 12930 [Not e] /usr/sbin/mysqld: Shutdown complete 6月 19 16:01:55 localhost.localdomain mysql-systemd-start[12907]: 2025-06-19 16:01:55 0 [Note] / usr/sbin/mysqld (mysqld 5.6.51) starting as process 12941 ... 6月 19 16:01:55 localhost.localdomain mysql-systemd-start[12907]: 2025-06-19 16:01:55 12941 [Not e] /usr/sbin/mysqld: Shutdown complete 6月 19 16:01:55 localhost.localdomain mysql-systemd-start[12907]: --defaults-file argument to my sqld_safe when starting the server 6月 19 16:01:56 localhost.localdomain mysqld_safe[12953]: 250619 16:01:56 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 16:01:56 localhost.localdomain mysqld_safe[12953]: 250619 16:01:56 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 16:01:56 localhost.localdomain mysqld_safe[12953]: 250619 16:01:56 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended 6月 19 16:11:55 localhost.localdomain systemd[1]: mysqld.service start-post operation timed out. Stopping. -- Subject: Unit mysqld.service has failed -- Unit mysqld.service has failed. 6月 19 16:11:55 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state. 6月 19 16:11:55 localhost.localdomain systemd[1]: mysqld.service failed. 6月 19 16:11:56 localhost.localdomain systemd[1]: mysqld.service holdoff time over, scheduling r estart. -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 16:11:56 localhost.localdomain mysqld_safe[19213]: 250619 16:11:56 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 16:11:56 localhost.localdomain mysqld_safe[19213]: 250619 16:11:56 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 16:11:57 localhost.localdomain mysqld_safe[19213]: 250619 16:11:57 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 16:23:58 localhost.localdomain mysql-systemd-start[27149]: 2025-06-19 16:23:58 0 [Note] / usr/sbin/mysqld (mysqld 5.6.51) starting as process 27165 ... 6月 19 16:24:00 localhost.localdomain mysql-systemd-start[27149]: 2025-06-19 16:24:00 0 [Note] / usr/sbin/mysqld (mysqld 5.6.51) starting as process 27201 ... 6月 19 16:24:02 localhost.localdomain mysql-systemd-start[27149]: --defaults-file argument to my sqld_safe when starting the server 6月 19 16:24:03 localhost.localdomain mysqld_safe[27239]: 250619 16:24:03 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 16:24:03 localhost.localdomain mysqld_safe[27239]: 250619 16:24:03 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql -- Subject: Unit mysqld.service has finished start-up -- Unit mysqld.service has finished starting up. -- Subject: Unit mysqld.service has begun shutting down -- Unit mysqld.service has begun shutting down. 6月 19 16:42:34 localhost.localdomain mysqld_safe[27239]: 250619 16:42:34 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 16:42:35 localhost.localdomain mysqld_safe[35199]: 250619 16:42:35 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 16:42:35 localhost.localdomain mysqld_safe[35199]: 250619 16:42:35 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql -- Subject: Unit mysqld.service has finished start-up -- Unit mysqld.service has finished starting up. 6月 19 17:22:37 localhost.localdomain sudo[52110]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl restart mysqld -- Subject: Unit mysqld.service has begun shutting down -- Unit mysqld.service has begun shutting down. 6月 19 17:22:38 localhost.localdomain mysqld_safe[35199]: 250619 17:22:38 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 17:22:39 localhost.localdomain mysqld_safe[52143]: 250619 17:22:39 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 17:22:39 localhost.localdomain mysqld_safe[52143]: 250619 17:22:39 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 17:22:41 localhost.localdomain mysqld_safe[52143]: 250619 17:22:41 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended 6月 19 17:23:26 localhost.localdomain sudo[52851]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl restart mysqld -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 17:23:26 localhost.localdomain mysqld_safe[52874]: 250619 17:23:26 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 17:23:26 localhost.localdomain mysqld_safe[52874]: 250619 17:23:26 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 17:23:28 localhost.localdomain mysqld_safe[52874]: 250619 17:23:28 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 17:24:11 localhost.localdomain mysqld_safe[53592]: 250619 17:24:11 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 17:24:11 localhost.localdomain mysqld_safe[53592]: 250619 17:24:11 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 17:24:14 localhost.localdomain mysqld_safe[53592]: 250619 17:24:14 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended 6月 19 17:25:12 localhost.localdomain systemd[1]: mysqld.service: control process exited, code=k illed status=9 -- Subject: Unit mysqld.service has failed -- Unit mysqld.service has failed. 6月 19 17:25:12 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state. 6月 19 17:25:12 localhost.localdomain systemd[1]: mysqld.service failed. 6月 19 17:25:12 localhost.localdomain systemd[1]: mysqld.service holdoff time over, scheduling r estart. -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 17:25:13 localhost.localdomain mysqld_safe[54465]: 250619 17:25:13 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 17:25:13 localhost.localdomain mysqld_safe[54465]: 250619 17:25:13 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 17:25:15 localhost.localdomain mysqld_safe[54465]: 250619 17:25:15 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended 6月 19 17:25:34 localhost.localdomain sudo[54929]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl restart mysqld -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 17:25:34 localhost.localdomain mysqld_safe[54953]: 250619 17:25:34 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 17:25:34 localhost.localdomain mysqld_safe[54953]: 250619 17:25:34 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 17:25:36 localhost.localdomain mysqld_safe[54953]: 250619 17:25:36 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended 6月 19 17:26:42 localhost.localdomain sudo[55901]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/pkill -9 mysqld 6月 19 17:26:49 localhost.localdomain sudo[55973]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/mysqld_safe --defaults-file=/etc/my.cnf 6月 19 17:31:13 localhost.localdomain sudo[58906]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl status mysqld 6月 19 17:33:49 localhost.localdomain sudo[60461]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl status mysqld 6月 19 17:33:59 localhost.localdomain sudo[60563]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/sbin/service mysqld status 6月 19 17:34:08 localhost.localdomain sudo[60663]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start mysqld 6月 19 17:34:32 localhost.localdomain sudo[60935]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start mysqld 6月 19 17:34:50 localhost.localdomain sudo[61150]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/sbin/service mysqld status 6月 19 17:35:34 localhost.localdomain systemd[1]: mysqld.service start-post operation timed out. Stopping. -- Subject: Unit mysqld.service has failed -- Unit mysqld.service has failed. 6月 19 17:35:34 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state. 6月 19 17:35:34 localhost.localdomain systemd[1]: mysqld.service failed. 6月 19 17:35:34 localhost.localdomain systemd[1]: mysqld.service holdoff time over, scheduling r estart. -- Subject: Unit mysqld.service has finished shutting down -- Unit mysqld.service has finished shutting down. -- Subject: Unit mysqld.service has begun start-up -- Unit mysqld.service has begun starting up. 6月 19 17:35:35 localhost.localdomain mysqld_safe[61625]: 250619 17:35:35 mysqld_safe Logging to '/var/log/mysqld.log'. 6月 19 17:35:35 localhost.localdomain mysqld_safe[61625]: 250619 17:35:35 mysqld_safe Starting m ysqld daemon with databases from /var/lib/mysql 6月 19 17:35:37 localhost.localdomain mysqld_safe[61625]: 250619 17:35:37 mysqld_safe mysqld fro m pid file /var/run/mysqld/mysqld.pid ended
最新发布
06-20
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值