查看服务器死机的日志文件,帮忙看下rac数据库服务器死机需重启的日志

最新推荐文章于 2023-09-23 18:36:44 发布
最新推荐文章于 2023-09-23 18:36:44 发布
阅读量350 收藏
点赞数
文章标签： 查看服务器死机的日志文件

ocssd.log如下：

[    CSSD]2008-06-18 11:37:58.443 [1210108256] >TRACE:   clssnmPollingThread: node jjgadb2 (2) missed(2) checkin(s)

[    CSSD]2008-06-18 11:38:02.450 [1210108256] >TRACE:   clssnmPollingThread: node jjgadb2 (2) missed(2) checkin(s)

[    CSSD]2008-06-18 11:38:04.454 [1210108256] >TRACE:   clssnmPollingThread: node jjgadb2 (2) missed(2) checkin(s)

[    CSSD]2008-06-18 11:38:54.346 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x76fe90) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:39:56.682 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x76fe90) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:40:59.020 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x76fe90) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:42:01.912 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x76fe90) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:42:15.309 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x76fe90) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:42:43.408 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x771e10) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:42:43.408 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7702d0) proc(0x774340) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:42:43.408 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x772800) proc(0x7e4a00) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:42:43.485 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e48e0) proc(0x7e8350) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:42:43.544 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e8a60) proc(0x7eb440) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:43:04.280 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e5220) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:44:06.739 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:45:09.076 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:46:11.637 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:47:13.991 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:48:16.327 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:49:18.669 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:50:21.018 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:51:23.385 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:52:15.740 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:52:25.773 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:52:43.835 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e5c60) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:52:43.836 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e51c0) proc(0x7e9c50) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:52:43.836 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e91b0) proc(0x76fa20) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:52:43.892 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770af0) proc(0x772b90) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:52:43.976 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x773350) proc(0x7eb940) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:53:28.122 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:54:30.499 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:55:32.860 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:56:35.239 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:57:37.592 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x779d60) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:58:39.944 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e6c40) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 11:58:43.321 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x776b20) proc(0x7e53a0) pid(2515) proto(10:2:1:1)

[    CSSD]2008-06-18 11:59:42.308 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e52f0) proc(0x7e90c0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:00:44.669 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e52f0) proc(0x7e90c0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:00:50.959 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e52f0) proc(0x7e8f90) pid(1686) proto(10:2:1:1)

[    CSSD]2008-06-18 12:01:09.866 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7e9790) proc(0x770570) pid(23088) proto(10:2:1:1)

[    CSSD]2008-06-18 12:01:47.053 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770b90) proc(0x772a80) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:02:16.128 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770440) proc(0x772ae0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:02:44.291 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770440) proc(0x7742a0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:02:44.291 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x773030) proc(0x7eb370) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:02:44.330 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7eb810) proc(0x7912e0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:02:44.361 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x71ea10) proc(0x7f2f70) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:02:44.445 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f3680) proc(0x7f6090) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:02:49.414 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770380) proc(0x7ed470) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:03:51.768 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770b90) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:04:54.159 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f0850) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:05:45.571 [1210108256] >TRACE:   clssnmPollingThread: node jjgadb1 (1) missed(2) checkin(s)

[    CSSD]2008-06-18 12:05:56.537 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770460) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:06:58.923 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f0850) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:08:01.288 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770b90) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:09:03.631 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f0850) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:10:05.998 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770460) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:11:08.344 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f0850) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:12:10.692 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770b90) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:12:16.438 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f0850) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:12:44.621 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f0850) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:12:44.622 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x791610) proc(0x7eb870) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:12:44.651 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7ed420) proc(0x7f3f20) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:12:44.684 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f45a0) proc(0x7729c0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:12:44.756 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x773140) proc(0x774320) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:13:13.041 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770b70) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:14:15.386 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x770b90) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:15:17.734 [1168148832] >TRACE:   clssgmClientConnectMsg: Connect from con(0x7f0850) proc(0x71e9b0) pid() proto(10:2:1:1)

[    CSSD]2008-06-18 12:16:08.937 [1220598112] >TRACE:   clsc_post: (0x6edda0) code 4, NS err (12603, 12532), transport (502, 22, 0)

[    CSSD]2008-06-18 12:16:08.940 [1220598112] >TRACE:   clsc_post: (0x6edda0) code 1, NS err (12603, 12532), transport (502, 22, 0)

[    CSSD]2008-06-18 12:16:08.940 [1220598112] >TRACE:   clsc_send: (0x75a5d0) ugblm (0x6edda0) lock failed, rc 3

[    CSSD]2008-06-18 12:16:08.940 [1220598112] >TRACE:   clsc_send_msg: (0x75a5d0) NS err (1, -1754094888), transport (-1754094888, -1754094888, -1754094888)

[    CSSD]2008-06-18 12:38:29.665 >USER:    Oracle Database 10g CSS Release 10.2.0.1.0 Production Copyright 1996, 2004 Oracle.  All rights reserved.

[  clsdmt]Listening to (ADDRESS=(PROTOCOL=ipc)(KEY=jjgadb1DBG_CSSD))

[    CSSD]2008-06-18 12:38:29.665 >USER:    CSS daemon log for node jjgadb1, number 1, in cluster crs

[    CSSD]2008-06-18 12:38:29.674 [2538110752] >TRACE:   clssscmain: local-only set to false

[    CSSD]2008-06-18 12:38:29.682 [2538110752] >TRACE:   clssnmReadNodeInfo: added node 1 (jjgadb1) to cluster

[    CSSD]2008-06-18 12:38:29.711 [2538110752] >TRACE:   clssnmReadNodeInfo: added node 2 (jjgadb2) to cluster

[    CSSD]2008-06-18 12:38:29.714 [1115699552] >TRACE:   clssnm_skgxnmon: skgxn init failed, rc 1

[    CSSD]2008-06-18 12:38:29.714 [2538110752] >TRACE:   clssnm_skgxnonline: Using vacuous skgxn monitor

[    CSSD]2008-06-18 12:38:29.715 [2538110752] >TRACE:   clssnmInitNMInfo: misscount set to 60

[    CSSD]2008-06-18 12:38:29.717 [2538110752] >TRACE:   clssnmDiskStateChange: state from 1 to 2 disk (0//dev/raw/raw3)

[    CSSD]2008-06-18 12:38:29.720 [2538110752] >TRACE:   clssnmDiskStateChange: state from 1 to 2 disk (1//dev/raw/raw4)

[    CSSD]2008-06-18 12:38:29.721 [2538110752] >TRACE:   clssnmDiskStateChange: state from 1 to 2 disk (2//dev/raw/raw5)

[    CSSD]2008-06-18 12:38:31.721 [1115699552] >TRACE:   clssnmDiskStateChange: state from 2 to 4 disk (0//dev/raw/raw3)

[    CSSD]2008-06-18 12:38:31.742 [1126189408] >TRACE:   clssnmDiskStateChange: state from 2 to 4 disk (1//dev/raw/raw4)

[    CSSD]2008-06-18 12:38:31.742 [1136679264] >TRACE:   clssnmDiskStateChange: state from 2 to 4 disk (2//dev/raw/raw5)

刘屿柠
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
linux服务器宕机如何查看日志,Linux死机重启后怎么查看实际日志？
weixin_32459553的博客
04-28 2万+
在程序的日常运维中，有时候也会遇到操作系统死机重启的情况，此时我们可能需要对此进行诊断。本文主要介绍如何查看Linux死机重启后的系统日志。具体操作系统信息如下：# lsb_release -aLSB Version: :core-4.1-amd64:core-4.1-noarchDistributor ID: CentOSDescription: CentOS Linux relea...
服务器运行一天死机,服务器死机怎么办?教你排除故障
weixin_35027170的博客
07-29 1979
我们大多数人都遇到过这种情况：服务器毫无反应，结果我们无法访问任务管理器，甚至无法访问服务器上的网络共享区。当然，不用说，出问题的似乎总是任务关键型服务器。这意味着，负责服务器的IT管理员难免会惊慌失措。处理服务器死机时，区别所谓的硬死机(call hang)与软死机(soft hang)显得很重要。这常常可以帮助我们根据在服务器上能执行什么操作、不能执行什么操作，至少能够诊断基本问题。比如说，如...
服务器假死笔记、日志按时间统计排查
最新发布
enthan809882的博客
09-23 303
服务器假死笔记、日志按时间统计排查
获取Linux内核卡死前的日志
六个九十度
09-10 7769
Linux侧开启rsyslog的UDP转发，Windows侧用Visual Syslog Server for Windows查看
某服务器经常死机。。所以写个一秒钟记录当前服务器状态的脚本。。
逆雪寒的天坑
11-25 1198
<br />服务器总是悄悄的死~~  活了以后又查不到啥问题。 所以写了这个脚本，不过自从写了这个脚本以后。服务器在也没死过。。。哈哈 辟邪作用<br /> <br /> <br />#!/bin/bash MT='/var/log/hezhou520.jk.log' do=0 (: > $MT) while true do if !(($do%10)); then do=0 (: > $MT)
Linux服务器创建oracle数据库RAC集群.docx
01-19
在本篇文档中，我们将详细探讨如何在Linux服务器上创建Oracle数据库RAC集群。RAC（Real Application Clusters）是Oracle数据库的一种高可用性解决方案，它允许多个服务器共享同一个数据库，提供故障转移和负载均衡...
为rac数据库增加控制文件
12-14
在Oracle Real Application Clusters (RAC)环境下，控制文件是数据库不可或缺的一部分，它记录了数据库的物理结构和元数据信息。当控制文件丢失或损坏时，数据库无法正常运行，因此通常需要创建至少两个或三个控制...
解决Oracle数据库归档日志占满磁盘空间问题
01-19
1、常用命令 SQL> show parameter log_archive_dest; SQL> archive log list; SQL> select * from V$FLASH_RECOVERY_AREA_USAGE; ARCHIVELOG 96.62 0 141 SQL> select sum(percent_space_used)*3/100 from v$flash_...
在Tomcat服务器下使用连接池连接Oracle数据库
12-16
在Tomcat服务器上使用连接池连接Oracle数据库是一个常见的任务，涉及到服务器配置、数据库连接管理和Java编程。以下将详细解释这个过程中的关键步骤和技术点。 首先，我们来看一下配置过程： 1. **修改web.xml文件...
Oracle RAC重启操作手册
04-04
这个文档详细的记录了重启Oracle rac的每一个步骤，重启的方法很多，这个可能不是最适合你的，但这个是有效的，这个文档是我给外行看的
RAC日志体系详解(原创)
czmmiao的专栏
12-05 404
简单介绍一下有关Oracle集群环境中日志体系结构，在遇到问题时，可以快速查找所需的日志文件，及时的定位问题。日志体系如下 Oracle集群日志的文件路径 $  tree -d $ORA_CRS_HOME/log /u01/app/oracle/product/10.2.0/crs/log |-- crs `-- czmmiao1     |-- admin     |-- ...
Oracle 11g RAC查看ASM日志、grid日志和DB日志
cuantangnie3915的博客
07-06 1995
查看ASM日志 [root@ATFDB1 ~]# su - grid [grid@ATFDB1 ~]$ sqlplus / as sysasm SQL*Plus: Release 11.2.0.3.0 Produc...
造成服务器死机的原因是什么？
weixin_44400506的博客
02-19 3127
服务器打不开，内存耗尽处于死机状态，这是怎么回事，什么引起的？要怎么解决？看完这篇文章。 　　问题： 　　服务器内存耗尽死机； 　　系统文件缓存耗费物理RAM； 　　一直对磁盘有大量的缓存读取请求。 　　原因是什么？ 　　在windows系统中，如果所有进程的请求都需要使用大量的内存，在物理内存中的内存页面数就会越来越多。如果不制止这些请求的话，那么内存页面数将会占用掉全部的内存。到了这种情况下时...
RAC常用日志总结
weixin_30877755的博客
11-10 113
12C RAC：ocssd启动失败log目录：/u01/app/grid/diag/crs/host02/crs/trace/alert.log 转载于:https://www.cnblogs.com/Clark-cloud-database/p/7814139.html
RAC架构中各种日志所在路径
weixin_34242819的博客
03-29 165
oracle 下的alert日志$ORACLE_BASE/diag/rdbms/orcl/orcl1/trace/alertorcl1.log grid 下的 alert 日志 $ORACLE_HOME/log/rac1/alertrac1.log css的日志$ORACLE_HOME/log/rac1/cssd/cssd.log ocssd.log crs的日志$ORACLE_HOME/log/...
服务器宕机，排查思路
weixin_69899223的博客
07-15 1651
服务器宕机，排查思路
服务器崩溃卡顿问题排查思路
李乾文的博客
07-12 2920
0x00 前言 本文讲述了服务器崩溃、卡顿时的排查思路。 0x00 前言 0x01 常见崩溃问题 (1) 首先看CPU、内存、和磁盘空间占用是否异常 (2) Session文件过多 (3) 日志文件过多 0x01 域名解析 0x02 Nginx服务 0x03 PHP服务 0x04 MySQL数据库
服务器死机故障判断以及处理办法
weixin_34310127的博客
12-08 846
服务器死机故障比较难以判断，经常碰到客户一段时间没有重启自动死机了也就是假死了!一般分为软件和硬件两个方面：　　1、软件故障：首先查看操作系统的系统日志，可以通过系统日志来判断部分造成死机的原因;电脑病毒的原因;系统软件的bug或漏洞造成的死机，这种故障需要在判断硬件无故障后做出，而且需要软件提供商提供帮助;软件使用不当或系统工作压力过大，可以请客户适当降低服务器的工作压力来...
linux主机宕机排查问题的方法
u012253351的博客
01-05 5743
Kdump 是一种有效的内存转储工具，启用 Kdump 后，生产内核将会保留一部分内存空间，用于在内核崩溃时通过 Kexec 快速启动到新的内核，这个过程不需要重启系统，因此可以转储崩溃的生产内核的内存镜像。如linux下的/var/log/下的log日志，包括message，内核报错日志demsg等等，sa记录，是记录cpu，内存等运行的性能文件，记录着运行时的cpu的运行状态如图所示。，cpu，内存，IO磁盘，应用BUG，内核BUG，硬件等。系统宕机的原因很多，需要我们细心的按照流程分析，
RHEL下Oracle RAC数据库安装配置详述
本篇文章是针对Oracle RAC数据库环境在Red Hat Enterprise Linux (RHEL)平台上的安装与配置手册。全文详细介绍了如何在一个高效、稳定的环境中部署和管理Oracle RAC，确保数据库系统的高可用性和性能。 首先，文章...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值