如题，为什么LTS的ListLogHistogram接口我调试总报LTS.0003 Invalid role，而我帐号是有日志读取权限的

我有一个站想用到华为云，不知道能不能在不动里面文章的同时，放到华为云吗？想提升一下速度，但是这个网站系统可能不一样，哪位大神帮我看下，如何转到华为云，域名 gzfynm.com 

vmcore-dmesg.txt:..............................................................................................[1643233.717506] Iptables-HTTP/S-IN: IN=bond0 OUT= MAC=b8:ce:f6:f1:f0:ce:7c:d9:a0:d8:52:22:08:00 SRC=10.151.10.139 DST=10.147.95.5 LEN=52 TOS=0x02 PREC=0x00 TTL=122 ID=5414 DF PROTO=TCP SPT=56560 DPT=443 WINDOW=64240 RES=0x00 CWR ECE SYN URGP=0  [1643248.444334] Unable to handle kernel paging request at virtual address 000000030000004c [1643248.444336] Mem abort info: [1643248.444336]   ESR = 0x96000004 [1643248.444338]   Exception class = DABT (current EL), IL = 32 bits [1643248.444339]   SET = 0, FnV = 0 [1643248.444339]   EA = 0, S1PTW = 0 [1643248.444340] Data abort info: [1643248.444341]   ISV = 0, ISS = 0x00000004 [1643248.444342]   CM = 0, WnR = 0 [1643248.444344] user pgtable: 4k pages, 48-bit VAs, pgdp = 00000000624182e4 [1643248.444345] [000000030000004c] pgd=0000000000000000 [1643248.444348] Internal error: Oops: 96000004 [#1] SMP [1643248.449378] Process conn309482 (pid: 34986, stack limit = 0x0000000067723cd1) [1643248.456655] CPU: 16 PID: 34986 Comm: conn309482 Kdump: loaded Tainted: G           OE     4.19.36-vhulk1907.1.0.h729.eulerosv2r8.aarch64 #1 [1643248.469288] Hardware name: Huawei S920S00K/BC82AMDGM, BIOS 1.77.K 06/28/2021 [1643248.476477] pstate: 60400009 (nZCv daif +PAN -UAO) [1643248.481424] pc : __kmalloc_node_track_caller+0x214/0x348 [1643248.486885] lr : __kmalloc_node_track_caller+0x6c/0x348 [1643248.492258] sp : ffff0000b38ebbe0 [1643248.495730] x29: ffff0000b38ebbe0 x28: ffffa03fdf779f00  [1643248.501192] x27: 0000000000000000 x26: 000000000000003c  [1643248.506654] x25: ffff803f7f407800 x24: ffff803f7f407800  [1643248.512116] x23: ffff000080861568 x22: 00000000ffffffff  [1643248.517578] x21: 00000000000001c0 x20: 0000000000410200  [1643248.523040] x19: 000000030000004c x18: 0000000000000000  [1643248.528502] x17: 0000000000000000 x16: 0000000000000000  [1643248.533962] x15: 0000000000000000 x14: 0000000000000000  [1643248.539423] x13: 0000000000000000 x12: 0000000000000010  [1643248.544885] x11: 0101010101010101 x10: 7f7f7fffffffff7f  [1643248.550347] x9 : 44670b96a6e5cbff x8 : 7fff7f7fff7f7f7f  [1643248.555809] x7 : fffdfeffb1ff3137 x6 : ffff802123aaa000  [1643248.561270] x5 : 0000000018ee63ee x4 : ffff803f7fa72660  [1643248.566732] x3 : ffff000080861568 x2 : 0000803efeb6c000  [1643248.572194] x1 : 0000803efeb6c000 x0 : 0000000000000000  [1643248.577657] Call trace: [1643248.580268]  __kmalloc_node_track_caller+0x214/0x348 [1643248.585385]  __kmalloc_reserve.isra.9+0x54/0xb0 [1643248.590067]  __alloc_skb+0x90/0x1b0 [1643248.593717]  cn_netlink_send_mult+0x148/0x268 [1643248.598227]  cn_netlink_send+0x40/0x50 [1643248.602133]  proc_comm_connector+0xd0/0xf8 [1643248.606387]  __se_sys_prctl+0x3e0/0x520 [1643248.610379]  __arm64_sys_prctl+0x28/0x38 [1643248.614458]  el0_svc_common+0x78/0x130 [1643248.618363]  el0_svc_handler+0x38/0x78 [1643248.622269]  el0_svc+0x8/0xc [1643248.625312] Code: 9400634f aa0003f9 17ffff9c b9402320 (f8606a66)  [1643248.631550] kernel fault(0x1) notification starting on CPU 16 [1643248.637441] kernel fault(0x1) notification finished on CPU 16 [1643248.643335] [kbox] catch die event on cpu 16............................................................................................

华为官网 反馈远程模拟器一会能用一会不能用，跟抽疯一样

过滤器从请求取requestid若没有则生成，随后放入MDC上下文中MDC（Mapped Diagnostic Context，映射调试上下文）是 log4j 和 logback 提供的一种方便在多线程条件下记录日志的功能。确保了多进程下进程之间在MDC存放的值是没有相互的影响的MDC的介绍package com.jerry.log;import org.slf4j.MDC;import org.springframework.stereotype.Component;import javax.servlet.*;import javax.servlet.http.HttpServletRequest;import javax.servlet.http.HttpServletResponse;import java.io.IOException;import java.util.UUID;/* * 在日志上下文增加参数，在日志中可以打印该参数，如RequestId，则日志配置：%d{yyyy-MM-dd HH:mm:ss.SSS} [%X{RequestId}] [%thread] %-5level %logger{36} - %msg%n * 则 RequestId 会打印在中括号里，%X{参数名} 是格式 **/@Componentpublic class MDCFilter implements Filter { /** * 设置响应头，响应头名字（惯例是大写） */ private static final String REQUEST_ID_HEADER = "RequestId"; /** * 设置到 MDC 里的key（惯例使用小驼峰，为了统一这里也用大写） */ private static final String REQUEST_ID = "RequestId"; @Override public void init(FilterConfig filterConfig) throws ServletException { } @Override public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException { HttpServletRequest httpRequest = (HttpServletRequest) request; HttpServletResponse httpResponse = (HttpServletResponse) response; String requestId = httpRequest.getHeader(REQUEST_ID_HEADER); if (requestId == null) { requestId = UUID.randomUUID().toString(); } // 还有更加准确的方法 String ip = getRequestSourceIp(httpRequest); MDC.put(REQUEST_ID, requestId); MDC.put("IP", ip); httpResponse.setHeader(REQUEST_ID_HEADER, requestId); try { chain.doFilter(request, response); } finally { MDC.clear(); } } @Override public void destroy() { } /** * 获取请求来源的IP,可以适应前置部署有Nginx等反向代理软件等的情况. HTTP_CLIENT_IP 无法伪造，所以放在第一个 * * @param request * @return */ public static String getRequestSourceIp(HttpServletRequest request) { String ip = request.getHeader("HTTP_CLIENT_IP"); if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) { ip = request.getHeader("HTTP_X_FORWARDED_FOR"); } if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) { ip = request.getHeader("HTTP_X_FORWARDED"); } if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) { ip = request.getHeader("HTTP_FORWARDED"); } if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) { ip = request.getHeader("X-FORWARDED-FOR"); } if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) { ip = request.getHeader("Proxy-Client-IP"); } if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) { ip = request.getHeader("WL-Proxy-Client-IP"); } if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) { ip = request.getRemoteAddr(); } return ip; }}配置过滤器（web.xml）<filter> <filter-name>MDCFilter</filter-name> <filter-class>com.jerry.log.MDCFilter</filter-class></filter><filter-mapping> <filter-name>MDCFilter</filter-name> <url-pattern>/*</url-pattern></filter-mapping>日志文件配置（log4j,properties）log4j.rootLogger = debug,stdout,E,I,Clog4j.appender.stdout = org.apache.log4j.ConsoleAppenderlog4j.appender.stdout.Target = System.outlog4j.appender.stdout.layout = org.apache.log4j.PatternLayoutlog4j.appender.stdout.layout.ConversionPattern = %-d{yyyy-MM-dd HH:mm:ss}|[%X{RequestId}][ %t:%r ] %m%n此处可以取到之前mdc上下文中的参数requestid和线程id转载自https://www.cnblogs.com/ruosu0909/p/RuoSuMDCRequestId.html

 Drain：一种基于固定深度树结构的在线日志解析方法论文名称：Drain: An Online Log Parsing Approach with Fixed Depth Tree作者：Pinjia He , Jieming Zhu , Zibin Zheng , and Michael R. Lyu发表时间：2017/6/30论文链接：http://www.cse.cuhk.edu.hk/lyu/_media/conference/pjhe_icws17.pdf?id=publications%3Aconference2&cache=cache推荐原因1、本文提出了一种高效的树结构来在线解析日志数据，将日志解析工作拆解为5个步骤，即根据具体的业务场景对日志进行简单的预处理、根据日志长度来搜索日志事件、根据日志第一个词来搜索日志事件、根据句子相似度来搜索日志事件，匹配日志事件或者更新日志事件，与大多数树结构的方法一样，作者也设计了一些剪枝的方法2、 作者提出的方法十分直观，并且灵活，与其说是一种日志分析算法，更多的是一种基于树结构的日志分析思路，一些其他基于树结构的日志处理方法亦可以很方便的整合到作者的模型中。

 Drain：一种基于固定深度树结构的在线日志解析方法论文名称：Drain: An Online Log Parsing Approach with Fixed Depth Tree作者：Pinjia He , Jieming Zhu , Zibin Zheng , and Michael R. Lyu发表时间：2017/6/30论文链接：http://www.cse.cuhk.edu.hk/lyu/_media/conference/pjhe_icws17.pdf?id=publications%3Aconference2&cache=cache推荐原因1、本文提出了一种高效的树结构来在线解析日志数据，将日志解析工作拆解为5个步骤，即根据具体的业务场景对日志进行简单的预处理、根据日志长度来搜索日志事件、根据日志第一个词来搜索日志事件、根据句子相似度来搜索日志事件，匹配日志事件或者更新日志事件，与大多数树结构的方法一样，作者也设计了一些剪枝的方法2、 作者提出的方法十分直观，并且灵活，与其说是一种日志分析算法，更多的是一种基于树结构的日志分析思路，一些其他基于树结构的日志处理方法亦可以很方便的整合到作者的模型中。转自，AI研习社，https://www.leiphone.com/category/academic/Is2BSkPUrXDA4Qt9.html

日志信息如下：[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.125.702 [VDEC] [VDM_HalProcess:918] [T85] Vdm ioctl fail, errno != EAGAIN. No retry.[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.125.908 [VDEC] [VDM_HalProcess:933] [T85] Failed to decode one frame, ret = -1, VdmRegState.VdmState = 0x360001[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.126.854 [VDEC] [message_process:1204] [T85] [MP] ERROR: VDEC_EVT_REPORT_VDM_DECODE_FAIL[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.126.935 [VDEC] [event_process:2301] [T85] [EP] OMX_ErrorVdmDecodeFail ERROR[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.126.973 [VDEC] [errorReport:227] [T85] report vdm decode error to user![ERROR] KERNEL(1929,sklogd):2020-10-16-17:27:55.127.169 [264635.854521]  [dvpp] [dvpp_vdec_irq_server 493] vdm_err_interrupt[ERROR] KERNEL(1929,sklogd):2020-10-16-17:27:55.127.224 [264635.854543]  [dvpp] [dvpp_vdec_vdm_process 223] wait_time_remain = 0x32,have vdm_error,p_vdm_backup_state->VdmState=0x360001 ,engine_id:0[ERROR] KERNEL(1929,sklogd):2020-10-16-17:27:55.127.255 [264635.854561]  [dvpp] [dvpp_vdec_engine_proc 332] dvpp_vdec_vdm_process failed, engine_id:0[ERROR] KERNEL(1929,sklogd):2020-10-16-17:27:55.127.283 [264635.854565]  [dvpp] [dvpp_ioctl_vdm 597] call proc failed:-61, engine_id:0[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.631.516 [VDEC] [VDMDRV_CheckDevice:529] [T85] VDM Time Out(507/3000 ms), VDM reset needed[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.631.607 [VDEC] [PostPro_GetH264MbGroup:493] [T85] [PostPro_GetH264MbGroup], DecSliceNum is 0, out of range[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.631.637 [VDEC] [VDMDRV_AfterDec:338] [T85] [VDMDRV_AfterDec], ISR process vdm timeout, FromInt is 0[ERROR] DVPP(10581,workspace_mind_studio_ev_atlas):2020-10-16-17:27:55.631.665 [VDEC] [VDMHAL_IMP_PrepareRepair:1655] [T85] [VDMHAL_IMP_PrepareRepair], FIRST_REPAIR Parameter Error

处理rtsp或循环处理离线视频，程序运行一段时间后，可能是几个小时或十几个小时，device侧会异常退出，日志如下：处理9路离线视频最后divice侧日志如下：[ERROR] KERNEL(1230,sklogd):2020-07-25-00:43:04.625.088 [25683.895916] arm-smmu-v3 140100000.smmu_a0: EVTQ overflow detected -- events lost  SUBSYSTEM=platform  DEVICE=+platform:140100000.smmu_a0[ERROR] KERNEL(1230,sklogd):2020-07-25-00:43:04.625.502 [25683.896037] arm-smmu-v3 140300000.smmu_a1: EVTQ overflow detected -- events lost  SUBSYSTEM=platform  DEVICE=+platform:140300000.smmu_a1[ERROR] KERNEL(1230,sklogd):2020-07-25-00:43:05.681.984 [25684.958274]  [devdrv] [devdrv_heart_beat_callback 1350] <swapper/5:0> receive ts exception msg, call mntn_system_error: 0xa4060006, time: 1595637785.679313, arg: 0.处理4路rtsp最后divice侧日志如下：[ERROR] TSCH(-1,null):2020-07-25-04:46:18.434.663 1 (cpuid:0) ai_cpu_dispatcher.c:870 ai_cpu_timeout_proc_done: ai_cpu_id= 0 response timeout![ERROR] TSCH(-1,null):2020-07-25-04:46:18.434.692 2 (cpuid:0) ai_cpu_dispatcher.c:887 ai_cpu_timeout_proc_done:  bs slot id is invalid [ERROR] TSCH(-1,null):2020-07-25-04:46:18.434.703 3 (cpuid:0) ai_cpu_dispatcher.c:870 ai_cpu_timeout_proc_done: ai_cpu_id= 1 response timeout![ERROR] TSCH(-1,null):2020-07-25-04:46:18.434.713 4 (cpuid:0) ai_cpu_dispatcher.c:887 ai_cpu_timeout_proc_done:  bs slot id is invalid 程序开始能跑起来，结果也能正确输出，看内存带宽基本都在60%以下，只是跑长时间就会出现问题，请问这些日志了反映了什么问题？

为了更直观的分析日志，该工具提供了错误日志分析，起播分析，播放流程分析，UI调用分析等功能。详情见附件

目的：通过工具，能分析出播放器常见的问题并给出解决建议。主要分析场景：1、  错误码统计分析。主要针对分析播放器日志中的错误码，整理出播放器的问题，并给出解决建议。一般现网问题80%都会有播放器错误码，通过错误码统计分析可以定位出绝大部分问题。错误码分析主要如下：a) 错误码规则说明; b) 错误码统计信息，包括日志中播放器总的错误日志数，关键错误统计及解决方案。2、  播放器主要流程分析，明确是否有异常流程日志或其他流程，进行说明。比如：DRM 的License 流程，在UI调用prepare接口之前需要设置DRMInfo信息给播放器。3、  起播分析，主要针对现网起播慢的情况进行分析，分析起播过程中每个阶段的耗时情况。4、  播放过程分析（关键事件响应：码率切换，音轨、字幕切换，seek、暂停/继续/停止等播放过程中的操作。 5、  UI 设置给播放器的参数信息。通过分析日志整理出UI设置给播放器的参数信息，如：播放URL，CAtype，视频类型，流类型，解码类型等。

[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.319.177 [46701.548474]  [dvpp] [print_all_reg 686] addr:0x0000ccf0,reg_val: 0x00000000 0x00000000 0x00000000 0x00000000[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.319.202 [46701.548475]  [dvpp] [print_all_reg 688] [ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.319.228 [46701.548514]  [dvpp] [dvpp_vdec_engine_proc 332] dvpp_vdec_vdm_process failed, engine_id:0[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.319.255 [46701.548518]  [dvpp] [dvpp_ioctl_vdm 597] call proc failed:-5, engine_id:0[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.319.288 [46701.550484]  [dvpp] [dvpp_vdec_irq_server 493] vdm_err_interrupt[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.320.925 [VDEC] [VDMDRV_AfterDec:355] [T27] Chan 1 ErrRatio = 95[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.322.467 [46701.555769]  [dvpp] [dvpp_vdec_vdm_process 223] wait_time_remain = 0x30,have vdm_error,p_vdm_backup_state->VdmState=0x360001 ,engine_id:1[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.322.527 [46701.555777]  [dvpp] [print_all_reg 682] [ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.323.640 [46701.555911]  [dvpp] [print_all_reg 686] addr:0x00001170,reg_val: 0x7ece4554 0x4f0f0c78 0xf52101ca 0xfa0b80e2[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.324.796 [46701.556036]  [dvpp] [print_all_reg 688] [ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.324.821 [46701.556083]  [dvpp] [dvpp_vdec_engine_proc 332] dvpp_vdec_vdm_process failed, engine_id:1[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.324.848 [46701.556088]  [dvpp] [dvpp_ioctl_vdm 597] call proc failed:-5, engine_id:1[ERROR] HDC(1706,graph_800):2020-04-17-09:15:30.349.077 [drvHdcMallocEx:872] >>> mmap failed mem_type(0), (error 12 Cannot allocate memory), addr (nil), len 4194304, flag 6[ERROR] HDC(1706,graph_800):2020-04-17-09:15:30.391.100 [drvHdcMallocEx:872] >>> mmap failed mem_type(0), (error 12 Cannot allocate memory), addr (nil), len 4194304, flag 6[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.403.556 [46701.638734]  [dvpp] [dvpp_vdec_irq_server 493] vdm_err_interrupt[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.403.616 [46701.638776]  [dvpp] [dvpp_vdec_vdm_process 223] wait_time_remain = 0x31,have vdm_error,p_vdm_backup_state->VdmState=0x360001 ,engine_id:0[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.403.650 [46701.638790]  [dvpp] [print_all_reg 682] [ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.432.774 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.432.828 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.432.891 [VDEC] [ReceivePacket:10393] [T27] nal_release_err[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.432.980 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=26) > dpb size(=2)[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.042 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.099 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.166 [VDEC] [ReceivePacket:10393] [T27] nal_release_err[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.258 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=27) > dpb size(=2)[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.321 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.376 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.437 [VDEC] [ReceivePacket:10393] [T27] nal_release_err[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.527 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=28) > dpb size(=2)[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.586 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.639 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.700 [VDEC] [ReceivePacket:10393] [T27] nal_release_err[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.786 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=29) > dpb size(=2)[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.844 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.433.898 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] HDC(1706,graph_800):2020-04-17-09:15:30.488.426 [drvHdcMallocEx:872] >>> mmap failed mem_type(0), (error 12 Cannot allocate memory), addr (nil), len 4194304, flag 6[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.488.784 [VDEC] [H264_DecOneNal:10172] [T27] ***** NAL: UNSUPPORT, nal_unit_type=4[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.488.936 [VDEC] [H264_DecSPS:9576] [T27] profile_idc =   254 error, try to decode as main profile.[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.489.027 [VDEC] [ProcessSPS:9054] [T27] bit_depth_luma(13) not equal 8.[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.489.098 [VDEC] [ProcessSPS:9070] [T27] bit_depth_chroma(9) not equal 8.[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.489.178 [VDEC] [ProcessSPS:9076] [T27] qpprime_y_zero_trans_bypass_flag not equal 0.[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.489.240 [VDEC] [H264_DecSPS:9633] [T27] Line 9633: SPS[1] decode error.[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.489.312 [VDEC] [H264_DecOneNal:10096] [T27] SPS decode error.[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.497.077 [VDEC] [VDMDRV_AfterDec:355] [T27] Chan 4 ErrRatio = 78[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.497.769 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=8) > dpb size(=2)[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.497.875 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.497.935 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.006 [VDEC] [ReceivePacket:10393] [T27] nal_release_err[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.138 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=9) > dpb size(=2)[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.201 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.256 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.318 [VDEC] [ReceivePacket:10393] [T27] nal_release_err[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.410 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=10) > dpb size(=2)[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.473 [VDEC] [H264_DecSlice:8244] [T27] init pic err, find next recover point or next valid sps, pps, or exit[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.528 [VDEC] [H264_DecOneNal:10070] [T27] Decoder Slice failed[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.592 [VDEC] [ReceivePacket:10393] [T27] nal_release_err[ERROR] DVPP(1706,graph_800):2020-04-17-09:15:30.498.682 [VDEC] [InitPic:6007] [T27] line 6007: frame gap(=11) > dpb size(=2)[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.498.694 [46701.727233]  [dvpp] [dvpp_vdec_irq_server 493] vdm_err_interrupt[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.498.738 [46701.727325]  [dvpp] [dvpp_vdec_vdm_process 223] wait_time_remain = 0x31,have vdm_error,p_vdm_backup_state->VdmState=0x360001 ,engine_id:0[ERROR] KERNEL(1183,sklogd):2020-04-17-09:15:30.498.772 [46701.727334]  [dvpp] [print_all_reg 682] 感觉像是dvpp h》264解码等调用内存分配失败的问题，但是这是在程序运行过程中出现的，之后程序还运行了一段时间。

老师，您好，我想请教一下"The format of the output file is invalid. error info: VM placement is invalid on host"这个是指输出文件格式有问题还是放置策略有问题呀？

本帖最后由 ES_Siyu 于 2018-3-16 10:38 编辑这篇文章讲述了如何在Kibana上对ES中的数据进行BI（商业智能）分析。本文旨在梳理整个流程，专注于功能的演示，故不会详述细节，具体可参考官方文档。 在这里我们将以apache log作为数据源进行分析。典型数据格式为： 12449 1 在Kibana上设置index的映射 · 在这里我们新建一个index为apache，type为logs的索引。映射字段包含日期，用户名，状态码，字节数，请求，主机，邮件。这些一一对应apache日志信息。 12451 · 接着导入Apache日志数据。具体过程省略。 · 在Kibana添加index pattern信息。在左边栏点击“Management”，如图所示，在kibana中添加“apache”索引模式。 12452 2 在Visualize添加可视化 2.1 饼状图在这里我们将统计用户访问的http状态码分布，以检测服务器运行的稳定程度。· 在左边栏点击“Visualize”，接着点击“Create a visualization”12453 · 选择饼状图“Pie”12454 · 点击选择“apache”索引12455 · 配置信息这里我们采用上一年的数据，因此选择“Previousyear”，可以在右上角看到这个选项。在“SliceSize”，选择“Aggregation”为“Unique Count”，“Field”为“host”。这是让出现相同ip的状态码只算一次。在“SplitSlices”，选择“Aggregation”为“Terms”，“Field”为“status”。这是让饼状图按照状态码来统计。在这张图，我们饼状图采用环装设计，这可以在左边栏点击“Options”，勾选“Donut”。12456 · 保存可视化，点击右上角“Save”，并且命名。这里命名为“status_unique_ip” 2.2 填充趋势图在这里我们将统计月度访问流量走势。· 添加新的可视化，点击“+”12457· 选择“Area”12458 · 同样点击“apache” · 配置信息在“Y-Axis”，选择“Aggregation”为“Sum”，“Field”为“bytes”。这是让y轴计算流量之和。在“X-Axis”，选择“Aggregation”为“Date Histogram”，“Field”为“date”，“interval”为“monthly”。这是让流量统计按月度计算。 12459 · 保存可视化，点击右上角“Save”，并且命名。这里命名为“monthly_flow”。 2.3 横向柱状图在这里我们将统计访问频率最高的request。· 添加新的可视化，点击“+”12460· 选择“HorizontalBar”12461· 同样点击“apache”· 配置信息在“Y-Axis”，选择“Aggregation”为“Count”。这是让y轴统计某条目的出现次数在“X-Axis”，选择“Aggregation”为“Terms”，“Field”为“request”，“Order By”为“metric：Count”，“Order”为“Descending”。这是让x轴统计客户发起的请求，按照从大到小的顺序排序。 12462 · 保存可视化，点击右上角“Save”，并且命名。这里命名为“frequent_request”。 2.4 纵向柱状图在这里我们将统计访问频率最高的ip。· 添加新的可视化，点击“+”12463· 选择“VerticalBar”12464· 同样点击“apache”· 配置信息在“Y-Axis”，选择“Aggregation”为“Count”。这是让y轴统计某条目的出现次数在“X-Axis”，选择“Aggregation”为“Terms”，“Field”为“host”，“Order By”为“metric：Count”，“Order”为“Descending”。这是让x轴统计不同客户ip出现的次数，按照从大到小的顺序排序。 12465 · 保存可视化，点击右上角“Save”，并且命名。这里命名为“frequent_ip”。 3 在Dashboard拼装可视化的结果 · 在左边栏点击“Dashboard”后，进入界面点击“Add”，新建dashboard。12466· 在面板上可以选择之前保存的可视化结果。12467· 依次点击后，可以把之前的结果全加载在面板上，通过拖拽和调整大小，可以如下图所示。12468