redis入门常见问题

最新推荐文章于 2024-07-09 21:38:06 发布
最新推荐文章于 2024-07-09 21:38:06 发布
阅读量502 收藏
点赞数
分类专栏： redis 文章标签： 数据库 网络 java
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/John8988/article/details/84923331
版权
本文主要介绍了在Spring中集成Redis时遇到的问题，包括'Error creating bean with name 'enableRedisKeyspaceNotificationsInitializer''的错误，该错误是由于Redis运行在保护模式下，未指定bind地址和认证密码。解决方法是修改redis.conf配置文件，取消bind 127.0.0.1的注释并设置protected-mode为no。此外，还提到了Redis的启动方式，可以通过指定配置文件启动。最后，给出了Redis的官方和中文网站资源。
摘要由CSDN通过智能技术生成

spring集成redis遇到的一些问题

1.Error creating bean with name 'enableRedisKeyspaceNotificationsInitializer' defined in class path resource 好像看不出报的什么错，继续往下看详细信息

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 
'enableRedisKeyspaceNotificationsInitializer' defined in class path resource 
[org/springframework/session/data/redis/config/annotation/web/http/RedisHttpSessionConfiguration.class]: 
Invocation of init method failed; 
nested exception is java.lang.IllegalStateException: Unable to configure Redis to keyspace notifications. 
See http://docs.spring.io/spring-session/docs/current/reference/html5/#api-redisoperationssessionrepository-sessiondestroyedevent

 详细报错信息如下：

 

23:30:46.489 [RMI TCP Connection(5)-127.0.0.1] ERROR org.springframework.web.servlet.DispatcherServlet - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'enableRedisKeyspaceNotificationsInitializer' defined in class path resource [org/springframework/session/data/redis/config/annotation/web/http/RedisHttpSessionConfiguration.class]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Unable to configure Redis to keyspace notifications. See http://docs.spring.io/spring-session/docs/current/reference/html5/#api-redisoperationssessionrepository-sessiondestroyedevent
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1710)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:583)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:502)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:312)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:310)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:200)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:760)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:868)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549)
	at org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:676)
	at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:642)
	at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:690)
	at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:558)
	at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:499)
	at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:172)
	at javax.servlet.GenericServlet.init(GenericServlet.java:160)
	at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1280)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1193)
	at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1088)
	at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5123)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5407)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
	at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1552)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:301)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:622)
	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:569)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:301)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
	at sun.rmi.transport.Transport$1.run(Transport.java:200)
	at sun.rmi.transport.Transport$1.run(Transport.java:197)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: Unable to configure Redis to keyspace notifications. See http://docs.spring.io/spring-session/docs/current/reference/html5/#api-redisoperationssessionrepository-sessiondestroyedevent
	at org.springframework.session.data.redis.config.ConfigureNotifyKeyspaceEventsAction.getNotifyOptions(ConfigureNotifyKeyspaceEventsAction.java:83)
	at org.springframework.session.data.redis.config.ConfigureNotifyKeyspaceEventsAction.configure(ConfigureNotifyKeyspaceEventsAction.java:57)
	at org.springframework.session.data.redis.config.annotation.web.http.RedisHttpSessionConfiguration$EnableRedisKeyspaceNotificationsInitializer.afterPropertiesSet(RedisHttpSessionConfiguration.java:286)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1769)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1706)
	... 64 common frames omitted
Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.; nested exception is redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.
	at org.springframework.data.redis.connection.jedis.JedisExceptionConverter.convert(JedisExceptionConverter.java:64)
	at org.springframework.data.redis.connection.jedis.JedisExceptionConverter.convert(JedisExceptionConverter.java:41)
	at org.springframework.data.redis.PassThroughExceptionTranslationStrategy.translate(PassThroughExceptionTranslationStrategy.java:44)
	at org.springframework.data.redis.FallbackExceptionTranslationStrategy.translate(FallbackExceptionTranslationStrategy.java:42)
	at org.springframework.data.redis.connection.jedis.JedisConnection.convertJedisAccessException(JedisConnection.java:181)
	at org.springframework.data.redis.connection.jedis.JedisServerCommands.convertJedisAccessException(JedisServerCommands.java:531)
	at org.springframework.data.redis.connection.jedis.JedisServerCommands.getConfig(JedisServerCommands.java:299)
	at org.springframework.data.redis.connection.DefaultedRedisConnection.getConfig(DefaultedRedisConnection.java:1119)
	at org.springframework.session.data.redis.config.ConfigureNotifyKeyspaceEventsAction.getNotifyOptions(ConfigureNotifyKeyspaceEventsAction.java:76)
	... 68 common frames omitted
Caused by: redis.clients.jedis.exceptions.JedisDataException: DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.
	at redis.clients.jedis.Protocol.processError(Protocol.java:127)
	at redis.clients.jedis.Protocol.process(Protocol.java:161)
	at redis.clients.jedis.Protocol.read(Protocol.java:215)
	at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
	at redis.clients.jedis.Connection.getBinaryMultiBulkReply(Connection.java:276)
	at redis.clients.jedis.Connection.getMultiBulkReply(Connection.java:269)
	at redis.clients.jedis.Jedis.configGet(Jedis.java:2630)
	at org.springframework.data.redis.connection.jedis.JedisServerCommands.getConfig(JedisServerCommands.java:297)
	... 70 common frames omitted

 86行，DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients.由于启用了保护模式，没有指定绑定地址，也没有向客户端请求身份验证密码，因此拒绝redis在保护模式下运行。

 

解决方案：

修改配置文件redis.conf

 

# accept connections only from clients running into the same computer it
# is running).
#
# IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
# JUST COMMENT THE FOLLOWING LINE.
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#bind 127.0.0.1

# Protected mode is a layer of security protection, in order to avoid that
# Redis instances left open on the internet are accessed and exploited.
#
# When protected mode is on and if:
#
# 1) The server is not binding explicitly to a set of addresses using the
#    "bind" directive.
# 2) No password is configured.
#
# The server only accepts connections from clients connecting from the
# IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
# sockets.
#
# By default protected mode is enabled. You should disable it only if
# you are sure you want clients from other hosts to connect to Redis
# even if no authentication is configured, nor a specific set of interfaces
# are explicitly listed using the "bind" directive.
protected-mode no

# Accept connections on the specified port, default is 6379 (IANA #815344).
# If port 0 is specified Redis will not listen on a TCP socket.
port 6379

# TCP listen() backlog.
#
# In high requests-per-second environments you need an high backlog in order
# to avoid slow clients connections issues. Note that the Linux kernel
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog

 如上 注释 bind 127.0.0.1

将 protected-mode yes 改为 protected-mode no

2.redis启动

通过启动参数告诉redis使用指定配置文件使用下面命令启动。

[root@eth-01 redis-3.2.8]# ./src/redis-server redis.conf

 redis.conf是一个默认的配置文件。我们可以根据需要使用自己的配置文件。

 

 

redis入门网站：

官方网站：https://redis.io/

中文网站：http://www.redis.net.cn/

http://www.redis.cn/

 

 

 

 

 

John8988
关注
专栏目录
Redis 常见问题
weixin_43260831的博客
07-13 819
Redis 常见问题 1.redis 是什么？都有哪些使用场景？ 2.redis 有哪些功能？ 3.redis 和 memecache 有什么区别？ 4.redis 为什么是单线程的？ 5.什么是缓存穿透？怎么解决？ 6.redis 支持的数据类型有哪些？ 7.redis 支持的 java 客户端都有哪些？ 8.jedis 和 redisson 有哪些区别？ 9.怎么保证缓存和数据库数据的一致性？...
Redis trouble18 -- Unable to configure Redis to keyspace notifications
weixin_39523456的博客
09-08 1925
解决方案 redis的服务端没有开启配置数据库通知的配置,在redis服务端执行下边命令即可 config setnotify-keyspace-events Egx config rewrite notify-keyspace-events数据库通知 数据库通知是Redis 2.8版本新增加的功能，这个功能可以让客户端通过订阅给定的频道或者模式，获知数据库中键变化，以及数据库中命令执行情况 分类： 键空间通知：“某个键执行了什么命令”的通知称为键空间通知（key-space n...
springboot集成redis错误：org.springframework.data.redis.connection.RedisConnection.getConfig(。。。。
cc1234565的博客
06-10 6100
将这个注释掉就行了
解决Error creating bean with name ‘enableRedisKeyspaceNotificationsInitializer‘ defined in class path
最新发布
Misnearch的博客
07-09 582
原因是spring-session调用了CONFIG命令来配置Keyspace notifications功能。而线上环境的redis基于权限的考虑，禁止应用服务执行CONFIG命令，就导致了应用在初始化时抛出此异常。可以去调spring-session依赖，将其注释，刷新maven。
解决监听redis key过期事件出现ERR unknown command `CONFIG`, with args beginning with: `GET`, `notify-keyspace-e
搬砖老农工的博客
03-26 1万+
监听redis key过期事件出现ERR unknown command `CONFIG`, with args beginning with: `GET`, `notify-keyspace-events`这个错误，主要是因为redis配置禁用了CONFIG命令，一些云服务出于安全考虑都会禁用CONFIG命令。 解决办法有两种，一种就是改配置，一种是基于代码层面解决。 方案一：改redis配置文件 注释掉rename-command CONFIG "" 方案二：代码层面 只要设置keys
Redis Config Get 命令
墨痕诉清风的博客
08-20 1088
Redis Config Get 命令用于获取 redis 服务的配置参数。在 Redis 2.4 版本中， 有部分参数没有办法用 CONFIG GET 访问，但是在最新的 Redis 2.6 版本中，所有配置参数都已经可以用 CONFIG GET 访问了。
spring循环依赖下使用@Async注解导致报错问题
weixin_44771989的博客
06-15 641
spring的三级缓存和循环依赖
Redis 入门指南.pdf
11-17
本指南将帮助初学者理解 Redis 的基本概念、安装与配置、数据类型以及常用命令，从而快速入门 Redis。 1. **Redis 简介** - Redis 源自意大利程序员 Salvatore Sanfilippo，最初是为了提高网站性能而设计的。 - ...
REDIS 入门指南pdf
09-03
- 常见框架如 Spring Data Redis 提供了高级封装，简化开发工作。 以上是 Redis 入门的基本知识点，深入学习 Redis 还需实践操作和理解其内部机制。通过阅读《REDIS 入门指南》这本书籍，你将能更全面地了解 Redis...
Java实战之Redis入门到精通
06-19
简介：本门课程主要讲解的是缓存中间件Redis常见且典型的数据结构、相关的核心技术栈及其典型的应用场景的实战，其中涉及到的相关代码实战主要是基于SpringBoot2.x搭建的项目进行实战实现的！ 其中的数据结构就包括...
redis入门超详细教程 包含redis各命令及使用教程
05-08
本教程将带你全面了解Redis，包括其基本数据类型、命令使用以及常见应用场景。 首先，让我们从Redis的数据格式开始。Redis支持五种基本数据类型： 1. 字符串（String）：最基础的类型，可以存储字符串、数字等。...
Redis入门
weixin_45486011的博客
03-12 1890
#Redis基础 Nosql：的发展史 Nosql是泛指非关系型sql存储数据，我们创建个.txt文件写完之后是不是需要CTL+S 去进行到存取磁盘中的过程，但是现在大部分开发工具都是自动去保存，想象一下 辛苦写的程序，突然断电导致笔记本关机，再次开机的情况下没有自动保存到电脑磁盘中 你的内心一定是崩溃的， NOSQL的出现就是为了处理大量数据的访问，把一些常用的数据存储在电脑磁盘中， 想象一下这个读写速度是很快的，为了处理高并发而提出的观点 比如一些大型的项目为了简化数据库的压力可以把常用的数据去存储在N
Result Maps collection already contains value for xxx.xxx.dao.BaseResultMap错误
jdk_wangtaida的博客
04-26 2224
前言： 我们在实际开发项目中，有的时候会用到mybatis的逆向工程，这个东西在某种程度的确很省事，但有时候也会因此出现bug,这篇文章讲解下如何解决题目中的bug。 正文： 一、复现问题 1.1 点击maven插件时，一不小心多点了一下，看mapper.xml时又没注意，这时候逆向工程生成xxxxMapper.xml,xxx实体类，xxxMapper时并不会重复生成xxx实体类和xxxM...
玩转Redis-研发也应该知道的Connection命令
zxiaofan.com
10-20 3327
《玩转Redis》系列文章主要讲述Redis的基础及中高级应用，文章基于Redis5.0.4 。Redis的连接往往是由程序完成，多数程序员并不关心，但掌握连接命令能提升自己的综合水平，真正了解整个Redis的使用过程。
Spring Session + Redis实现分布式Session共享
热门推荐
叉叉哥的BLOG
09-30 7万+
通常情况下，Tomcat、Jetty等Servlet容器，会默认将Session保存在内存中。如果是单个服务器实例的应用，将Session保存在服务器内存中是一个非常好的方案。但是这种方案有一个缺点，就是不利于扩展。目前越来越多的应用采用分布式部署，用于实现高可用性和负载均衡等。那么问题来了，如果将同一个应用部署在多个服务器上通过负载均衡对外提供访问，如何实现Session共享？实际上实现Sessi
Spring Session java连接redis 失败解决方案
jaffreyen的博客
01-29 5798
日志提示连接拒绝, 是因为redis默认的protected-mode默认为yes 解决方案1: 进入redis-cli  输入命令 CONFIG SET protected-mode no 解决方案2. 在redis目录下的redis.conf配置文件中增加 protected-mode no 方案2需要重启redis 设置成功, 重启项目就没有这个错误了
Redis禁用Config命令后SpringBoot启动报错：ERR config is disabled command
lpch0825的博客
12-29 5630
1、背景说明 项目属于Spring Boot，本身一直都是正常的，由于最近安全活动禁用了Redis的Config命令，导致项目重启报错： org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'enableRedisKeyspaceNotificationsInitializer' defined in class path resource [org/...
Error creating bean with name 'enableRedisKeyspaceNotificationsInitializer'
weixin_44146570的博客
04-02 446
Error creating bean with name ‘enableRedisKeyspaceNotificationsInitializer’ defined in class path resource
Redis入门与集群部署指南：实战与解决常见问题
Redis的学习涵盖了从基础概念、缓存机制的理解，到实际操作、集群部署策略和问题解决，是一个深入学习和实践的过程。掌握Redis的关键在于理解其核心原理，熟练运用各种数据结构，并了解如何配置和管理一个健壮的...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值